camel-mllp is vulnerable to Insertion of Sensitive Information into Log File
55
CVE Score
Medium
Insertion of Sensitive Information into Log File
Before the fix, the camel-mllp component logged protected health information from HL7 v2 messages: TcpSocketConsumerRunnable.run wrote each received message, partial payload, and out-of-band data through convertToPrintFriendlyString with no logPhi check, and logPhi defaulted to true, so PHI reached ordinary application logs even when an operator set logPhi=false on those paths. Any network peer that could open a TCP connection to the MLLP listener port supplied that content without authentication. HL7 v2 messages carry patient data, so anyone with access to those logs could read PHI. The fix defaults logPhi to false and routes every payload log statement through convertToLoggableString, which substitutes <PHI suppressed> when logPhi is disabled.
Upgrade the org.apache.camel:camel-mllp package to a fixed release on your branch: 4.18.5, 4.22.1.
You are affected if you are using a version that falls within the vulnerable range and receive HL7 v2 messages over MLLP on a listener port reachable by network peers, without explicitly setting logPhi to false.
4.0.0 - 4.18.4
Fixed in 4.18.54.19.0 - 4.22.0
Fixed in 4.22.1camel-mllp is vulnerable to Insertion of Sensitive Information into Log File in versions 4.0.0 - 4.18.4 and 4.19.0 - 4.22.0.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.