Vulnerability	Vulnerable Version
M Insertion of Sensitive Information into Log File Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via `MllpSocketBuffer` logging in the MLLP component. A low-privileged local attacker can send HL7 data that is logged by default because `logPhi` is enabled; even with `logPhi` disabled, a partial payload that times out after an end-of-block followed by trailing bytes, or bytes sent before `START_OF_BLOCK`, are logged. This exposes patient information in ordinary application logs, where it is subject to the deployment’s log access and retention controls. Notes At the logging step, each entry is limited by `logPhiMaxBytes` (default 5120 bytes), so larger HL7 payloads are not fully exposed in a single log entry. Workarounds Set `logPhi=false` on the MLLP component to suppress payload logging on paths that honor the option; two paths will still log payload content until the fix is applied. Restrict access to application logs to limit exposure of patient data that may still be logged. How to fix Insertion of Sensitive Information into Log File? Upgrade `org.apache.camel:camel-mllp` to version 4.18.5, 4.22.1 or higher.	[4.0.0,4.18.5)[4.19.0,4.22.1)

Insertion of Sensitive Information into Log File

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File via MllpSocketBuffer logging in the MLLP component. A low-privileged local attacker can send HL7 data that is logged by default because logPhi is enabled; even with logPhi disabled, a partial payload that times out after an end-of-block followed by trailing bytes, or bytes sent before START_OF_BLOCK, are logged. This exposes patient information in ordinary application logs, where it is subject to the deployment’s log access and retention controls.

Notes

At the logging step, each entry is limited by logPhiMaxBytes (default 5120 bytes), so larger HL7 payloads are not fully exposed in a single log entry.

Workarounds

Set logPhi=false on the MLLP component to suppress payload logging on paths that honor the option; two paths will still log payload content until the fix is applied.
Restrict access to application logs to limit exposure of patient data that may still be logged.

How to fix Insertion of Sensitive Information into Log File?

Upgrade org.apache.camel:camel-mllp to version 4.18.5, 4.22.1 or higher.

[4.0.0,4.18.5)[4.19.0,4.22.1)

Go back to all versions of this package