{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-27938 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-27938 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-27938 is a medium-severity vulnerability in postalserver postal, published on 11 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-27938 and fix it if it is affected.\n\nWhat it is: CVE-2024-27938 is a medium-severity vulnerability in postalserver postal, published on 11 Mar 2024. 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-2024-27938 in the wild and no public exploit code.\n\nAffected product: postalserver postal. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2024-27938/ (Markdown: https://insights.sbomify.com/CVE-2024-27938/index.md)","id":"CVE-2024-27938","markdown":"https://insights.sbomify.com/CVE-2024-27938/index.md","name":"CVE-2024-27938","record":{"aliases":["GHSA-j42r-6c99-hqf2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SMTP mail server","requires_auth":"none","summary":"Attackers can spoof incoming emails via SMTP smuggling, bypassing sender authorization checks in Postal mail server.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"postal","vendor":"postalserver"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"Postal is an open source SMTP server. Postal versions less than 3.0.0 are vulnerable to SMTP Smuggling attacks which may allow incoming e-mails to be spoofed. This, in conjunction with a cooperative outgoing SMTP service, would allow for an incoming e-mail to be received by Postal addressed from a server that a user has 'authorised' to send mail on their behalf but were not the genuine author of the e-mail. Postal is not affected for sending outgoing e-mails as email is re-encoded with `\u003cCR\u003e\u003cLF\u003e` line endings when transmitted over SMTP. This issue has been addressed and users should upgrade to Postal v3.0.0 or higher. Once upgraded, Postal will only accept End of DATA sequences which are explicitly `\u003cCR\u003e\u003cLF\u003e.\u003cCR\u003e\u003cLF\u003e`. If a non-compliant sequence is detected it will be logged to the SMTP server log. There are no workarounds for this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SMTP Smuggling in Postal","id":"CVE-2024-27938","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"File upload in RUGGEDCOM CROSSBOW","id":"CVE-2024-27939"},"packages":[],"prev":{"headline":"glpi Users emails enumeration","id":"CVE-2024-27937"},"products":["postal"],"published":"2024-03-11","related":[{"cvss_score":8.1,"headline":"Postal has HTML injection / XSS in message view","id":"CVE-2026-25529","kev_date_added":null,"published":"2026-03-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-27","vendors":["postalserver"]},"summary":"Attackers can spoof incoming emails via SMTP smuggling, bypassing sender authorization checks in Postal mail server.","url":"https://insights.sbomify.com/CVE-2024-27938/"}