Apache CXF: Denial of Service and sensitive data exposure in logs
Apache Software Foundation Apache CXF
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.cxf:cxf-core Maven |
|
|
Apache Software Foundation Apache CXF
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.cxf:cxf-core Maven |
|
|
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.
From the CVE record · apache
Apache CXF can read an entire temporary file for a large stream-based message into memory and log it, potentially allowing an attacker to cause an out-of-memory denial of service. If temporary-file encryption is configured, the file contents can also be written to logs unencrypted. The input does not specify whether exploitation requires authentication or user interaction.
Teams using Maven package org.apache.cxf:cxf-core in versions before 3.5.11, 3.6.0 through 3.6.5, 4.0.0 through 4.0.6, or 4.1.0 should check their deployments.