PatchTheCVElibpam4j vulnerabilities and fixes
Recent CVEs affecting libpam4j, with upgrade or downgrade steps. 1 tracked.
libpam4j has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2018-01-18. Highest priority: CVE-2017-12197 (score 46/100).
- CVE-2017-12197 MEDIUM 6.5 UPGRADE MITIGATE It was found that libpam4j up to and including 1.8 did not properly validate user accounts when authenticating
FAQ
How do I fix libpam4j vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is libpam4j being exploited right now?
None of the tracked libpam4j CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libpam4j CVE should I patch first?
CVE-2017-12197 currently ranks highest (46/100): It was found that libpam4j up to and including 1.8 did not properly validate user accounts when authenticating.