CVE-2010-2656 json
The IBM BladeCenter with Advanced Management Module (AMM) firmware build ID BPET48L, and possibly other versions before 4.7 and 5.0, stores…
published 16y ago modified 4mo ago also EUVD-2010-2660
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 1
- Exploit-DB
Summary
The IBM BladeCenter with Advanced Management Module (AMM) firmware build ID BPET48L, and possibly other versions before 4.7 and 5.0, stores sensitive information under the web root with insufficient access control, which allows remote attackers to download (1) logs or (2) core files via direct requests, as demonstrated by a request for private/sdc.tgz.
Is CVE-2010-2656 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-14237)
- Published
Exploit prediction
2.46% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-14237 IBM Bladecenter Management - Multiple Web Application Vulnerabilities webapps, 2010-07-06
- securityfocus.com http://www.securityfocus.com/bid/41383 referenced PoC, tagged "exploit" by a source, unverified
- dsecrg.com http://dsecrg.com/pages/vul/show.php?id=154 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
exploit-db.com
/exploits/14237/
exploit
-
securityfocus.com
/bid/41383
vdb-entry, exploit
-
dsecrg.com
/pages/vul/show.php?id=154
exploit
-
osvdb.org
/66123
vdb-entry
Sources
- CVE List CVE-2010-2656
- NVD CVE-2010-2656
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.