CVE-2010-4598 json
Directory traversal vulnerability in Ecava IntegraXor 3.6.4000.0 and earlier allows remote attackers to read arbitrary files via a .. (dot…
published 2010-12-23 15 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4564
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 26.5%
- EPSS 26.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
Directory traversal vulnerability in Ecava IntegraXor 3.6.4000.0 and earlier allows remote attackers to read arbitrary files via a .. (dot dot) in the file_name parameter in an open request.
Timeline
- First public exploit (EDB-15802)
- Published
Exploit prediction
26.48% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-15802 ecava IntegraXor 3.6.4000.0 - Directory Traversal remote, 2010-12-21
- securityfocus.com http://www.securityfocus.com/bid/45535 referenced PoC, tagged "exploit" by a source, unverified
- aluigi.org http://aluigi.org/adv/integraxor_1-adv.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-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
exploit-db.com
/exploits/15802
exploit
-
securityfocus.com
/bid/45535
vdb-entry, exploit
-
aluigi.org
/adv/integraxor_1-adv.txt
exploit
-
vupen.com
/english/advisories/2010/3304
vdb-entry, vendor-advisory
- integraxor.com /blog/integraxor-3-6-scada-security-issue-20101222-0323-vulnerability-note
-
secunia.com
/advisories/42730
third-party-advisory
- us-cert.gov /control_systems/pdf/ICS-ALERT-10-355-01.pdf
-
kb.cert.org
/vuls/id/979776
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2010-4598
- NVD CVE-2010-4598
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.