vertx-mail-client is vulnerable to CRLF Injection
69
CVE Score
Medium
CRLF Injection
Before the fix, MailMessage stored header names, header values, and attachment metadata with only null checks, so a CR or LF in any of these strings passed into the SMTP DATA section and injected extra headers or body content, such as a hidden Bcc copy, into outgoing mail. A bare LF in a display name also bypassed Q-encoding because the mail encoder treated LF as allowed. This matters when an unauthenticated client or a signed-in user feeding a web form into the mail client can control these fields and the application sends mail on their behalf. The fix rejects CR and LF in header names, values, and attachment metadata by throwing an exception and encodes LF in display names.
Upgrade the io.vertx:vertx-mail-client package to the patched version.
You are affected if you are using a version that falls within the vulnerable range and let an unauthenticated client or a signed-in user supply mail header names, values, or attachment metadata containing CR or LF.
3.0.0 - 4.5.34
Fixed in 4.5.355.0.0 - 5.1.9
Fixed in 5.1.105.2.0 - 5.2.0
Fixed in 5.2.1vertx-mail-client is vulnerable to CRLF Injection in versions 5.2.0 - 5.2.0, 5.0.0 - 5.1.9 and 3.0.0 - 4.5.34.
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.