CVE-2011-1560 json
solid.exe in IBM solidDB before 4.5.181, 6.0.x before 6.0.1067, 6.1.x and 6.3.x before 6.3.47, and 6.5.x before 6.5.0.3 uses a password-has…
published 2011-04-05 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1561
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.0%
- EPSS 4.0% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
solid.exe in IBM solidDB before 4.5.181, 6.0.x before 6.0.1067, 6.1.x and 6.3.x before 6.3.47, and 6.5.x before 6.5.0.3 uses a password-hash length specified by the client, which allows remote attackers to bypass authentication via a short length value.
Exploit prediction
3.99% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-255 Credentials Management Errors
References
-
ibm.com
/support/docview.wss?uid=swg21474552
vendor-advisory
-
osvdb.org
/71494
vdb-entry
-
secunia.com
/advisories/44030
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/66455
vdb-entry
-
vupen.com
/english/advisories/2011/0854
vdb-entry
- zerodayinitiative.com /advisories/ZDI-11-115/
Sources
- CVE List CVE-2011-1560
- NVD CVE-2011-1560
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.