PatchTheCVEpam-pgsql vulnerabilities and fixes
Recent CVEs affecting pam-pgsql, with upgrade or downgrade steps. 3 tracked.
Also searched as: pam pgsql.
pam-pgsql has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2004-05-04. Highest priority: CVE-2003-0672 (score 48/100).
- CVE-2004-0366 HIGH 7.5 UPGRADE SQL injection vulnerability in the libpam-pgsql library before 0.5.2 allows attackers to execute arbitrary SQL
- CVE-2003-0672 HIGH 7.5 DOWNGRADE Format string vulnerability in pam-pgsql 0.5.2 and earlier allows remote attackers to execute arbitrary code v
- CVE-2001-1369 HIGH 7.5 DOWNGRADE Leon J Breedt pam-pgsql before 0.5.2 allows remote attackers to execute arbitrary SQL code and bypass authenti
FAQ
How do I fix pam-pgsql 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 pam-pgsql being exploited right now?
None of the tracked pam-pgsql CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which pam-pgsql CVE should I patch first?
CVE-2003-0672 currently ranks highest (48/100): Format string vulnerability in pam-pgsql 0.5.2 and earlier allows remote attackers to execute arbitrary code v.