Apache CXF: Denial of Service and sensitive data exposure in logs
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.5.11, 3.6.6, 4.0.7, 4.1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Apache CXF stores large stream based messages as temporary files on the local filesystem. A bug was introduced which means that the entire temporary file is read into memory and then logged. An attacker might be able to exploit this to cause a denial of service attack by causing an out of memory exception. In addition, it is possible to configure CXF to encrypt temporary files to prevent sensitive credentials from being cached unencrypted on the local filesystem, however this bug means that the cached files are written out to logs unencrypted. Users are recommended to upgrade to versions 3.5.11, 3.6.6, 4.0.7 or 4.1.1, which fixes this issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Apache Software Foundation Apache CXF
From 3.5.10 · fixed in 3.5.11; From 3.6.5 · fixed in 3.6.6; From 4.0.6 · fixed in 4.0.7; From 4.1.0 · fixed in 4.1.1
- org.apache.cxf:cxf-coreMaven
fixed in 3.5.11
- org.apache.cxf:cxf-coreMaven
From 3.6.0 · fixed in 3.6.6
- org.apache.cxf:cxf-coreMaven
From 4.0.0 · fixed in 4.0.7
- org.apache.cxf:cxf-coreMaven
From 4.1.0 · fixed in 4.1.1