Skip to content
Fencer Intel
high 7.4

CVE-2021-44549 json

SMTPS server hostname not checked when making TLS connection to SMTPS server

published 4y ago modified 4mo ago also GHSA-c69w-jj56-834w , EUVD-2021-2501

cvss
7.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

Apache Sling Commons Messaging Mail provides a simple layer on top of JavaMail/Jakarta Mail for OSGi to send mails via SMTPS. To reduce the risk of "man in the middle" attacks additional server identity checks must be performed when accessing mail servers. For compatibility reasons these additional checks are disabled by default in JavaMail/Jakarta Mail. The SimpleMailService in Apache Sling Commons Messaging Mail 1.0 lacks an option to enable these checks for the shared mail session. A user could enable these checks nevertheless by accessing the session via the message created by SimpleMessageBuilder and setting the property mail.smtps.ssl.checkserveridentity to true. Apache Sling Commons Messaging Mail 2.0 adds support for enabling server identity checks and these checks are enabled by default. - https://javaee.github.io/javamail/docs/SSLNOTES.txt - https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html - https://github.com/eclipse-ee4j/mail/issues/429

Patch / fix

  • maven org.apache.sling:org.apache.sling.commons.messaging.mail 2.0
  • jenkins ocp tools 4.12 2.462.3.1730119132-3.el8
  • jenkins-2-plugins ocp tools 4.12 4.12.1730119231-1.el8
  • jenkins ocp tools 4.13 2.462.3.1729839924-3.el8
  • jenkins-2-plugins ocp tools 4.13 4.13.1729840148-1.el8
  • jenkins ocp tools 4.14 2.462.3.1729839727-3.el8
  • jenkins-2-plugins ocp tools 4.14 4.14.1729839844-1.el8
  • jenkins ocp tools 4.15 2.462.3.1729837947-3.el8
  • jenkins-2-plugins ocp tools 4.15 4.15.1729838165-1.el8

red hat advisories RHSA-2024:8886RHSA-2024:8887RHSA-2024:8885RHSA-2024:8884

Is CVE-2021-44549 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-44549 updated cvss 7.4

angus-mail: Enabling Secure Server Identity Checks for Safer SMTPS Communication

  • Red Hat build of Apache Camel 4 for Quarkus 3 angus-mail
    affected: workaround, no fix planned “Will not fix”
  • Red Hat build of Apache Camel for Spring Boot 4 angus-mail
    affected: workaround, no fix available
  • Red Hat Build of Keycloak angus-mail
    affected: workaround, no fix planned “Will not fix”
  • Red Hat OpenShift Developer Tools and Services for OCP 4.12 jenkins 2.462.3.1730119132-3.el8, jenkins-2-plugins 4.12.1730119231-1.el8
    fixed: vendor fix RHSA-2024:8886
  • Red Hat OpenShift Developer Tools and Services for OCP 4.13 jenkins 2.462.3.1729839924-3.el8, jenkins-2-plugins 4.13.1729840148-1.el8
    fixed: vendor fix RHSA-2024:8887
  • Red Hat OpenShift Developer Tools and Services for OCP 4.14 jenkins 2.462.3.1729839727-3.el8, jenkins-2-plugins 4.14.1729839844-1.el8
    fixed: vendor fix RHSA-2024:8885
  • Red Hat OpenShift Developer Tools and Services for OCP 4.15 jenkins 2.462.3.1729837947-3.el8, jenkins-2-plugins 4.15.1729838165-1.el8
    fixed: vendor fix RHSA-2024:8884
  • Red Hat build of Quarkus Native builder
    fixed: vendor fix RHSA-2024:7676
show 1 more
  • Red Hat OpenShift Serverless angus-mail Red Hat Data Grid 8 angus-mail Red Hat JBoss Enterprise Application Platform 8 angus-mail
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.08% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N
GitHub 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.sling:org.apache.sling.commons.messaging.mail
<2.0
2.0

Affected products

  • Apache Software Foundation Apache Sling Commons Messaging Mail

Classification

Weakness
  • CWE-295 Improper Certificate Validation
  • CWE-297 Improper Validation of Certificate with Host Mismatch

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.