Skip to content

← Public intelligence

Maven package

org.apache.commons:commons-email

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5MavenPublished

    Improper Input Validation in Apache Commons Email

    CVE-2017-9801 · GHSA-p7vm-phxx-g722

    Affected
    • Maven org.apache.commons:commons-email >= 1.0, <= 1.4
    Fixed in
    1.5· Vendor fix available
    Issue
    When a call-site passes a subject for an email that contains line-breaks in Apache Commons Email 1.0 through 1.4, the caller can add arbitrary SMTP headers.

    Recommended action: Upgrade to 1.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5MavenPublished

    Improper Input Validation Apache Commons Email

    CVE-2018-1294 · GHSA-v7cm-w955-pj6g

    Affected
    • Maven org.apache.commons:commons-email < 1.5
    Fixed in
    1.5· Vendor fix available
    Issue
    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).

    Recommended action: Upgrade to 1.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →