| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Nextapp Echo 2.0.1/2.1.0/3.0. Affected by this issue is some unknown functionality of the component XML Parser. Performing a manipulation results in input validation. This vulnerability is known as CVE-2009-5135. Furthermore, an exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Nextapp Echo 2.0.1/2.1.0/3.0. This affects an unknown functionality of the component XML Parser. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality. The summary by CVE is:
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.
The weakness was published 03/10/2009 (Website). The advisory is shared at sec-consult.com. This vulnerability is uniquely identified as CVE-2009-5135 since 05/01/2013. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 2.1.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (49167), Exploit-DB (8191), OSVDB (52889†) and Secunia (SA34218†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Echo 2.1.0
Timeline
03/10/2009 🔍03/10/2009 🔍
03/10/2009 🔍
05/01/2013 🔍
05/02/2013 🔍
03/24/2015 🔍
01/11/2025 🔍
Sources
Advisory: sec-consult.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2009-5135 (🔍)
GCVE (CVE): GCVE-0-2009-5135
GCVE (VulDB): GCVE-100-64065
X-Force: 49167
Secunia: 34218 - Echo2 XML Processing Information Disclosure Vulnerability, Moderately Critical
OSVDB: 52889 - NextApp Echo2 Engine XML External Entity Processing Privilege Escalation
Vupen: ADV-2009-0653
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/24/2015 15:54Updated: 01/11/2025 11:51
Changes: 03/24/2015 15:54 (58), 02/26/2019 09:40 (4), 01/11/2025 11:51 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.