{"answers":{"affected":"2 open source packages ship an affected version, including nodemailer. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7769 in the wild and no public exploit code.","fix":"Upgrade nodemailer to 6.4.16 or later.","what":"CVE-2020-7769 is a high-severity command injection vulnerability in nodemailer, published on 12 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7769 and fix it if it is affected.\n\nWhat it is: CVE-2020-7769 is a high-severity command injection vulnerability in nodemailer, published on 12 Nov 2020. 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-2020-7769 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nodemailer (npm): affected all versions; fixed in 6.4.16\n- nodemailer (npm): affected all versions; fixed in 6.4.16\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-2020-7769/ (Markdown: https://insights.sbomify.com/CVE-2020-7769/index.md)","id":"CVE-2020-7769","markdown":"https://insights.sbomify.com/CVE-2020-7769/index.md","name":"CVE-2020-7769","record":{"aliases":["CLSA-2026-1784596339","DEBIAN-CVE-2020-7769","GHSA-48ww-j4fc-435p","UBUNTU-CVE-2020-7769"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js email library","requires_auth":"none","summary":"Attackers can inject arbitrary command flags via crafted email addresses in the sendmail transport, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"nodemailer","vendor":"nodemailer"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H/E:P/RL:U/RC:C","version":"3.1"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"This affects the package nodemailer before 6.4.16. Use of crafted recipient email addresses may result in arbitrary command flag injection in sendmail transport for sending mails.","ecosystems":["npm"],"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":"Command Injection","id":"CVE-2020-7769","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":2,"n_references":4,"next":{"headline":"Prototype Pollution","id":"CVE-2020-7770"},"packages":[{"ecosystem":"npm","fixed":["6.4.16"],"introduced":["0"],"last_affected":[],"package":"nodemailer","purl":null,"source":"GHSA-48ww-j4fc-435p"},{"ecosystem":"npm","fixed":["6.4.16"],"introduced":["0"],"last_affected":[],"package":"nodemailer","purl":"pkg:npm/nodemailer","source":"GHSA-48ww-j4fc-435p"}],"prev":{"headline":"Prototype Pollution","id":"CVE-2020-7768"},"products":["nodemailer"],"published":"2020-11-12","related":[{"cvss_score":7.5,"headline":"Nodemailer: nodemailer: denial of service via crafted email address header","id":"CVE-2025-14874","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":6.3,"headline":"HTTP Header Injection","id":"CVE-2021-23400","kev_date_added":null,"published":"2021-06-29"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can inject arbitrary command flags via crafted email addresses in the sendmail transport, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2020-7769/"}