LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1294: If a user of Apache Commons Email (typically an application programmer) passes unvalidated input as the so-...

If a user of Apache Commons Email (typically an application programmer) passes unvalidated input as the so-called "Bounce Address", and that input contains line-breaks, then the email details (recipients, contents, etc.) might be manipulated. Mitigation: Users should upgrade to Commons-Email 1.5. You can mitigate this vulnerability for older versions of Commons Email by stripping line-breaks from data, that will be passed to Email.setBounceAddress(String).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Apache Commons Email before 1.5 can mishandle an application-supplied bounce address if that value includes line breaks. In applications that let users influence this field, an attacker may alter email details such as recipients or message content. The issue is narrow but relevant where email-sending workflows process untrusted input. Exposure is limited to applications using Apache Commons Email versions before 1.5 and setting the bounce address from untrusted or insufficiently validated data. Systems not using setBounceAddress, or not letting user-controlled data reach it, are less likely exposed. Prioritize remediation for internet-facing or customer-driven email workflows that use older Commons Email. The business risk is targeted manipulation of outgoing email behavior, not a broadly exploitable platform compromise based on the supplied evidence. Mitigation focus: Upgrade Apache Commons Email to version 1.5 or later.; Strip line breaks before data reaches Email.setBounceAddress(String).; Review vendor guidance before relying on compensating controls..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-1294 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Commons Emailversions prior to 1.5Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.