| Summary: | pam-python new security issue CVE-2019-16729 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | Dan Fandrich <dan> |
| Status: | RESOLVED INVALID | QA Contact: | Sec team <security> |
| Severity: | major | ||
| Priority: | Normal | CC: | zombie_ryushu |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | pam-python-1.0.6-3.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2020-10-13 18:27:25 CEST
Sorry; I had my head down fixing autobuild problems and forgot. I'll take care of getting this into mga7. Status:
NEW =>
ASSIGNED I looked at the upstream change to fix this issue and found that we already include the relevant line (in load_user_module) in 1.0.6 via the -fedora patchset. So, it looks like Mageia is not vulnerable to this in either mga7 or Cauldron, which is probably why I didn't open a bug. :-) Status:
ASSIGNED =>
RESOLVED |