5
CVSSv2

CVE-2011-2483

Published: 25/08/2011 Updated: 23/04/2024
CVSS v2 Base Score: 5 | Impact Score: 2.9 | Exploitability Score: 10
VMScore: 445
Vector: AV:N/AC:L/Au:N/C:P/I:N/A:N

Vulnerability Summary

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

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

php php

postgresql postgresql

openwall crypt blowfish

Vendor Advisories

Debian Bug report logs - #631283 CVE-2011-2483 crypt_blowfish: 8-bit character mishandling allows different password pairs to produce the same hash Package: php5-suhosin; Maintainer for php5-suhosin is (unknown); Reported by: Luciano Bello <luciano@debianorg> Date: Wed, 22 Jun 2011 14:51:06 UTC Severity: serious Tags: sec ...
PostgreSQL incorrectly handled blowfish passwords ...
Several security issues were fixed in PHP ...
magnum discovered that the blowfish password hashing used amongst others in PostgreSQL contained a weakness that would give passwords with 8 bit characters the same hash as weaker equivalents For the oldstable distribution (lenny), this problem has been fixed in postgresql-83 version 8316-0lenny1 For the stable distribution (squeeze), this pro ...
Several vulnerabilities have been discovered in PHP, the web scripting language The Common Vulnerabilities and Exposures project identifies the following issues: CVE-2011-1938 The UNIX socket handling allowed attackers to trigger a buffer overflow via a long path name CVE-2011-2483 The crypt_blowfish function did not properly handle 8-bit ...
A signedness issue was found in the way the crypt() function in the PostgreSQL pgcrypto module handled 8-bit characters in passwords when using Blowfish hashing Up to three characters immediately preceding a non-ASCII character (one with the high bit set) had no effect on the hash result, thus shortening the effective password length This made br ...
PHP before 537 does not properly check the return values of the malloc, calloc, and realloc library functions, which allows context-dependent attackers to cause a denial of service (NULL pointer dereference and application crash) or trigger a buffer overflow by leveraging the ability to provide an arbitrary value for a function argument, related ...

Github Repositories

Portable password hashing framework for PHP. Uses the bcrypt and the SHA2 crypt() alternative schemes.

About Portable password hashing framework for PHP Originally inspired by phpass v03, hence the name PasswordHash2 However, it resembles none of the phpass framework If the crypt() does not implement the desired scheme, a pure PHP implementation is available My proposed SHA2 schemes are, well, proposed Unless they don't gain some traction, you won't see them impl