CVE-2014-6577 json
Unspecified vulnerability in the XML Developer's Kit for C component in Oracle Database Server 11.2.0.3, 11.2.0.4, 12.1.0.1, and 12.1.0.2 a…
published 11y ago modified 4mo ago also EUVD-2014-6456
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.6%
- EPSS 3.6% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the XML Developer's Kit for C component in Oracle Database Server 11.2.0.3, 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows remote authenticated users to affect confidentiality via unknown vectors. NOTE: the previous information is from the January 2015 CPU. Oracle has not commented on the original researcher's claim that this is an XML external entity (XXE) vulnerability in the XML parser, which allows attackers to conduct internal port scanning, perform SSRF attacks, or cause a denial of service via a crafted (1) http: or (2) ftp: URI.
Patch / fix
Is CVE-2014-6577 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 FencerExploit prediction
3.56% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- blog.netspi.com https://blog.netspi.com/advisory-xxe-injection-oracle-database-cve-2014-6577/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:L/Au:S/C:C/I:N/A:N |
Classification
- Technology feeds
References
-
oracle.com
/technetwork/topics/security/cpujan2015-1972971.html
patch, vendor-advisory
-
blog.netspi.com
/advisory-xxe-injection-oracle-database-cve-2014-6577/
exploit
-
securityfocus.com
/bid/72139
vdb-entry
-
securitytracker.com
/id/1031572
vdb-entry
Sources
- CVE List CVE-2014-6577
- NVD CVE-2014-6577
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.