CVE-2003-0672: Format string vulnerability in pam-pgsql 0.5.2 and earlier allows remote attackers to execute arbitrary code v

This month

HIGH 7.5DOWNGRADE

CVE-2003-0672 is a high-severity flaw (CVSS 7.5) affecting pam-pgsql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Format string vulnerability in pam-pgsql 0.5.2 and earlier allows remote attackers to execute arbitrary code via the username that isp rovided during authentication, which is not properly handled when recording a log message.

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	3.1% (top 12%)
CISA exploited list	No
Published	2003-08-27
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: leon j breedt

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2003-08-27 04:00 UTCPublished CVE record published
2026-06-16 22:02 UTCUpdated Record last modified

leon j breedt pam-pgsql DOWNGRADE

Affected: 0.5.1 · 0.5.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.5.1

1. Check installed version

apt-cache policy pam-pgsql || rpm -q pam-pgsql || pam-pgsql --version

2. No fixed release: DOWNGRADE to a release before 0.5.1 (Debian / Ubuntu)

apt-cache madison pam-pgsql sudo apt install pam-pgsql=<VERSION_BEFORE_0.5.1> sudo apt-mark hold pam-pgsql

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pam-pgsql sudo dnf downgrade pam-pgsql-<VERSION_BEFORE_0.5.1> sudo dnf versionlock add pam-pgsql

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2003-0672?

pam-pgsql: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2003-0672 being exploited?

CVE-2003-0672 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2003-0672 affect?

CVE-2003-0672 affects pam-pgsql. Severity is high (CVSS 7.5). Format string vulnerability in pam-pgsql 0.5.2 and earlier allows remote attackers to execute arbitrary code via the username that isp rovided during authentication, which is not properly handled when recording a log message.

How urgent is CVE-2003-0672?

Priority 48/100. High severity

Related CVEs

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-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

References

← Back to latest CVEs