{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.sling:org.apache.sling.commons.messaging.mail. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-44549 in the wild and no public exploit code.","fix":"Upgrade org.apache.sling:org.apache.sling.commons.messaging.mail to 2.0 or later.","what":"CVE-2021-44549 is a high-severity vulnerability in Apache Sling Commons Messaging Mail, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-44549 and fix it if it is affected.\n\nWhat it is: CVE-2021-44549 is a high-severity vulnerability in Apache Sling Commons Messaging Mail, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-44549 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.sling:org.apache.sling.commons.messaging.mail (Maven): affected all versions; fixed in 2.0\n- org.apache.sling:org.apache.sling.commons.messaging.mail (Maven): affected all versions; fixed in 2.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-44549/ (Markdown: https://insights.sbomify.com/CVE-2021-44549/index.md)","id":"CVE-2021-44549","markdown":"https://insights.sbomify.com/CVE-2021-44549/index.md","name":"CVE-2021-44549","record":{"aliases":["GHSA-c69w-jj56-834w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java mail library","requires_auth":"none","summary":"The library fails to verify SMTPS server identity by default, allowing man-in-the-middle attacks unless explicitly configured or upgraded.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"sling_commons_messaging_mail","vendor":"apache"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SMTPS server hostname not checked when making TLS connection to SMTPS server","id":"CVE-2021-44549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":2,"n_references":1,"next":{"headline":"Access Control vulnerability within CoreNLP","id":"CVE-2021-44550"},"packages":[{"ecosystem":"Maven","fixed":["2.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.sling:org.apache.sling.commons.messaging.mail","purl":null,"source":"GHSA-c69w-jj56-834w"},{"ecosystem":"Maven","fixed":["2.0"],"introduced":["0"],"last_affected":[],"package":"org.apache.sling:org.apache.sling.commons.messaging.mail","purl":"pkg:maven/org.apache.sling/org.apache.sling.commons.messaging.mail","source":"GHSA-c69w-jj56-834w"}],"prev":{"headline":"Apache Solr information disclosure vulnerability through DataImportHandler","id":"CVE-2021-44548"},"products":["Apache Sling Commons Messaging Mail"],"published":"2021-12-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Apache Software Foundation"]},"summary":"The library fails to verify SMTPS server identity by default, allowing man-in-the-middle attacks unless explicitly configured or upgraded.","url":"https://insights.sbomify.com/CVE-2021-44549/"}