CVE-2009-5135 json
The Java XML parser in Echo before 2.1.1 and 3.x before 3.0.b6 allows remote attackers to read arbitrary files via a request containing an…
published 13y ago modified 4mo ago also EUVD-2009-5090
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.9%
- EPSS 9.9% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
The Java XML parser in Echo before 2.1.1 and 3.x before 3.0.b6 allows remote attackers to read arbitrary files via a request containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.
Is CVE-2009-5135 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-8191)
- Published
Exploit prediction
9.92% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-8191 NextApp Echo < 2.1.1 - XML Injection remote, 2009-03-10
- sec-consult.com https://www.sec-consult.com/fxdata/seccons/prod/temedia/advisories_txt/20090305-0_echo_nextapp_xml_injection.txt 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-20 Improper Input Validation
References
-
exploit-db.com
/exploits/8191/
exploit
-
sec-consult.com
/fxdata/seccons/prod/temedia/advisories_txt/20090305-0_echo_nextapp_xml_injection.txt
exploit
-
secunia.com
/advisories/34218
third-party-advisory, vendor-advisory
-
echo.nextapp.com
/site/node/5742
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49167
vdb-entry
-
securityfocus.com
/archive/1/501637/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2009/0653
vdb-entry
Sources
- CVE List CVE-2009-5135
- NVD CVE-2009-5135
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.