# CVE-2011-2483: Weak cryptography in n/a > Attackers can recover cleartext passwords from hashes due to improper 8-bit character handling in the crypt_blowfish library. - **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Aug 2011 - **Updated:** 6 Aug 2024 - **Also known as:** DEBIAN-CVE-2011-2483, DSA-2340-1, GHSA-f6xx-pp35-hmmv, RHSA-2011:1377, RHSA-2011:1378, openSUSE-SU-2024:10312-1 ## What is CVE-2011-2483? CVE-2011-2483 is a medium-severity vulnerability in Php Php, published on 25 Aug 2011. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-310 ## Which versions are affected by CVE-2011-2483? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `postgresql` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-contrib` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-docs` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-jdbc` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-libs` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-pl` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-python` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-server` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-tcl` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql-test` | Red Hat:enterprise_linux:4::as | All versions | 0:7.4.30-3.el4 | | `postgresql` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-contrib` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-docs` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-jdbc` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-libs` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-pl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-python` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-server` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-tcl` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql-test` | Red Hat:enterprise_linux:4::desktop | All versions | 0:7.4.30-3.el4 | | `postgresql` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-contrib` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-docs` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-jdbc` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-libs` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-pl` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-python` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-server` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-tcl` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql-test` | Red Hat:enterprise_linux:4::es | All versions | 0:7.4.30-3.el4 | | `postgresql` | Red Hat:enterprise_linux:4::ws | All versions | 0:7.4.30-3.el4 | | `postgresql-contrib` | Red Hat:enterprise_linux:4::ws | All versions | 0:7.4.30-3.el4 | | `postgresql-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:7.4.30-3.el4 | | `postgresql-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:7.4.30-3.el4 | Products: Openwall Crypt Blowfish, Php Php, Postgresql Postgresql. ## How do I fix CVE-2011-2483? Upgrade to a fixed version. ## Is CVE-2011-2483 being exploited? There is no known exploitation of CVE-2011-2483 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2011-2483 and fix it if it is affected. What it is: CVE-2011-2483 is a medium-severity vulnerability in Php Php, published on 25 Aug 2011. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2011-2483 in the wild and no public exploit code. Affected product: Php Php. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2011-2483/ (Markdown: https://insights.sbomify.com/CVE-2011-2483/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2011-2483 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-2483 - OSV: https://osv.dev/vulnerability/CVE-2011-2483 --- From sbomify Insights: https://insights.sbomify.com/CVE-2011-2483/ Summaries are generated and may contain mistakes; the official description above is the record.