CVE-2011-2483: crypt_blowfish before 1.1, as used in PHP before 5.3.7 on certain platforms, PostgreSQL before 8.4.9, and othe

Q: How do I fix CVE-2011-2483?

php: upgrade to 5.3.7; postgresql: upgrade to 8.2.22, 8.3.16, 8.4.9, 9.0.5; crypt blowfish: upgrade to 1.1. Exact commands for each OS are on this page.

Q: Is CVE-2011-2483 being exploited?

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

Q: What does CVE-2011-2483 affect?

CVE-2011-2483 affects php, postgresql, crypt blowfish. Severity is medium (CVSS 5.0). crypt_blowfish before 1.1, as used in PHP before 5.3.7 on certain platforms, PostgreSQL before 8.4.9, and other products, does not properly handle 8-bit characters, which makes it easier for context-dependent attackers to determine a cleart

Q: How urgent is CVE-2011-2483?

Priority 41/100. EPSS top 8%: very likely to be exploited

This month

MEDIUM 5.0UPGRADEUPGRADEUPGRADE

CVE-2011-2483 is a medium-severity flaw (CVSS 5.0) affecting php, postgresql, crypt blowfish. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

crypt_blowfish before 1.1, as used in PHP before 5.3.7 on certain platforms, PostgreSQL before 8.4.9, and other products, does not properly handle 8-bit characters, which makes it easier for context-dependent attackers to determine a cleartext password by leveraging knowledge of a password hash.

Why this priority

EPSS top 8%: very likely to be exploited

A fixed release or distro patch exists.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	5.0% (top 8%)
CISA exploited list	No
Weakness	CWE-310
Published	2011-08-25
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: openwall · php · postgresql

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

Am I affected?

Timeline

2011-08-25 14:22 UTCPublished CVE record published
2026-06-16 23:31 UTCUpdated Record last modified

php php UPGRADE

Affected: < 5.3.7

Fixed in: 5.3.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy php || rpm -q php || php --version

2. UPGRADE to 5.3.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade php

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade php

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

postgresql postgresql UPGRADE

Affected: >= 8.2.0 and < 8.2.22 · >= 8.3.0 and < 8.3.16 · >= 8.4.0 and < 8.4.9 · >= 9.0.0 and < 9.0.5

Fixed in: 8.2.22, 8.3.16, 8.4.9, 9.0.5

Safe to downgrade to: a release before 8.2.0

1. Check installed version

apt-cache policy postgresql || rpm -q postgresql || postgresql --version

2. UPGRADE to 8.2.22 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade postgresql

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade postgresql

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 8.2.0 (Debian / Ubuntu)

apt-cache madison postgresql sudo apt install postgresql=<VERSION_BEFORE_8.2.0> sudo apt-mark hold postgresql

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list postgresql sudo dnf downgrade postgresql-<VERSION_BEFORE_8.2.0> sudo dnf versionlock add postgresql

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.

openwall crypt blowfish UPGRADE

Affected: < 1.1

Fixed in: 1.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy crypt-blowfish || rpm -q crypt-blowfish || crypt-blowfish --version

2. UPGRADE to 1.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade crypt-blowfish

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade crypt-blowfish

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2011-2483?

php: upgrade to 5.3.7; postgresql: upgrade to 8.2.22, 8.3.16, 8.4.9, 9.0.5; crypt blowfish: upgrade to 1.1. Exact commands for each OS are on this page.

Is CVE-2011-2483 being exploited?

CVE-2011-2483 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-2011-2483 affect?

CVE-2011-2483 affects php, postgresql, crypt blowfish. Severity is medium (CVSS 5.0). crypt_blowfish before 1.1, as used in PHP before 5.3.7 on certain platforms, PostgreSQL before 8.4.9, and other products, does not properly handle 8-bit characters, which makes it easier for context-dependent attackers to determine a cleart

How urgent is CVE-2011-2483?

Priority 41/100. EPSS top 8%: very likely to be exploited

Software pages

PHP vulnerabilities · PostgreSQL vulnerabilities

Related CVEs

CVE-2026-109619 HIGH 8.1 EXPLOITED UPGRADE MITIGATE PHP Stale Internal Request-State Vulnerability
CVE-2026-109618 CRITICAL 9.8 EXPLOITED UPGRADE MITIGATE PHP Memory Corruption Vulnerability
CVE-2026-91768 MEDIUM 6.5 UPGRADE The IPv6 branch of the FastCGI client access check compares only the first 12 bytes of a 16-byte IPv6 address,
CVE-2026-92842 MEDIUM 5.9 UPGRADE The convert.base64-encode, convert.quoted-printable-encode and convert.quoted-printable-decode stream filters
CVE-2026-91767 MEDIUM 6.5 UPGRADE php_openssl_matches_wildcard_name() in ext/openssl/xp_ssl.c underflows the length argument passed to memchr()

References

← Back to latest CVEs