{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-12063 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-12063 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-12063 is a medium-severity vulnerability in n/a, published on 24 Apr 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-12063 and fix it if it is affected.\n\nWhat it is: CVE-2020-12063 is a medium-severity vulnerability in n/a, published on 24 Apr 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-12063 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-12063/ (Markdown: https://insights.sbomify.com/CVE-2020-12063/index.md)","id":"CVE-2020-12063","markdown":"https://insights.sbomify.com/CVE-2020-12063/index.md","name":"CVE-2020-12063","record":{"aliases":["GHSA-5wj2-9pm2-74vm"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Postfix mail server","requires_auth":"none","summary":"Attackers can bypass sender login restrictions in Postfix by using homoglyph characters in email addresses, allowing spoofed outbound messages.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"postfix","vendor":"postfix"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"A certain Postfix 2.10.1-7 package could allow an attacker to send an email from an arbitrary-looking sender via a homoglyph attack, as demonstrated by the similarity of \\xce\\xbf to the 'o' character. This is potentially relevant when the /etc/postfix/sender_login feature is used, because a spoofed outbound message that uses a configured sender address is blocked with a \"Sender address rejected: not logged in\" error message, but a spoofed outbound message that uses a homoglyph of a configured sender address is not blocked. NOTE: some third parties argue that any missed blocking of spoofed outbound messages - except for exact matches to a sender address in the /etc/postfix/sender_login file - is outside the design goals of Postfix and thus cannot be considered a Postfix vulnerability","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2020-12063","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-12066"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2020-12062"},"products":["n/a"],"published":"2020-04-24","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-10140","kev_date_added":null,"published":"2018-04-16"},{"cvss_score":6.9,"headline":"Path traversal in n/a","id":"CVE-2009-2939","kev_date_added":null,"published":"2009-09-21"},{"cvss_score":6.9,"headline":"Path traversal in n/a","id":"CVE-2008-4977","kev_date_added":null,"published":"2008-11-06"},{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2011-1720","kev_date_added":null,"published":"2011-05-13"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2011-0411","kev_date_added":null,"published":"2011-03-16"},{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2012-0811","kev_date_added":null,"published":"2014-10-01"},{"cvss_score":6.2,"headline":"Privilege escalation in n/a","id":"CVE-2008-2936","kev_date_added":null,"published":"2008-08-18"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can bypass sender login restrictions in Postfix by using homoglyph characters in email addresses, allowing spoofed outbound messages.","url":"https://insights.sbomify.com/CVE-2020-12063/"}