Sling Commons Messaging Mail vulnerabilitiesRanked by how likely they are to be used.
Sling Commons Messaging Mail is made by Apache. We track 1 published vulnerability in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Sling Commons Messaging Mail, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Sling Commons Messaging Mail vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Sling Commons Messaging Mail's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Sling Commons Messaging Mail flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.1%CVE-2021-44549High
Apache Sling Commons Messaging Mail provides a simple layer on top of JavaMail/Jakarta Mail for OSGi to send mails via SMTPS.
Running Sling Commons Messaging Mail? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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
- Matched to
- Sling Commons Messaging Mail on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 1 published vulnerability listed under the name Sling Commons Messaging Mail, across 1 version.
None of Sling Commons Messaging Mail's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Sling Commons Messaging Mail. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.