CVE-2010-2655 json
Directory traversal vulnerability in private/file_management.php on the IBM BladeCenter with Advanced Management Module (AMM) firmware buil…
published 16y ago modified 4mo ago also EUVD-2010-2659
- cvss
- 4.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in private/file_management.php on the IBM BladeCenter with Advanced Management Module (AMM) firmware build ID BPET48L, and possibly other versions before 4.7 and 5.0, allows remote authenticated users to list arbitrary directories and possibly have unspecified other impact via a .. (dot dot) in the DIR parameter.
Is CVE-2010-2655 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.29% chance of exploitation in the next 30 days, higher than 83% 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 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
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
/66124
vdb-entry
Sources
- CVE List CVE-2010-2655
- NVD CVE-2010-2655
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.