{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-1720 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2011-1720 is a medium-severity memory corruption vulnerability in n/a, published on 13 May 2011. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-1720 and fix it if it is affected.\n\nWhat it is: CVE-2011-1720 is a medium-severity memory corruption vulnerability in n/a, published on 13 May 2011. 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-2011-1720 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-2011-1720/ (Markdown: https://insights.sbomify.com/CVE-2011-1720/index.md)","id":"CVE-2011-1720","markdown":"https://insights.sbomify.com/CVE-2011-1720/index.md","name":"CVE-2011-1720","record":{"aliases":["DEBIAN-CVE-2011-1720","GHSA-8j5r-6hhw-hf9g","RHSA-2011:0843"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Postfix SMTP server","requires_auth":"none","summary":"Remote attackers can cause denial of service or execute arbitrary code via heap memory corruption in Postfix when specific SASL authentication methods are enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"postfix","vendor":"postfix"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"The SMTP server in Postfix before 2.5.13, 2.6.x before 2.6.10, 2.7.x before 2.7.4, and 2.8.x before 2.8.3, when certain Cyrus SASL authentication methods are enabled, does not create a new server handle after client authentication fails, which allows remote attackers to cause a denial of service (heap memory corruption and daemon crash) or possibly execute arbitrary code via an invalid AUTH command with one method followed by an AUTH command with a different method.","ecosystems":["Red Hat:enterprise_linux:4::as","Red Hat:enterprise_linux:4::desktop","Red Hat:enterprise_linux:4::es","Red Hat:enterprise_linux:4::ws","Red Hat:enterprise_linux:5::server","Red Hat:enterprise_linux:6::server"],"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":"Memory corruption in n/a","id":"CVE-2011-1720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2011"},"n_packages":18,"n_references":18,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2011-1721"},"packages":[{"ecosystem":"Red Hat:enterprise_linux:4::as","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix","purl":"pkg:rpm/redhat/postfix","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::as","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix-debuginfo","purl":"pkg:rpm/redhat/postfix-debuginfo","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::as","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix-pflogsumm","purl":"pkg:rpm/redhat/postfix-pflogsumm","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::desktop","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix","purl":"pkg:rpm/redhat/postfix","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::desktop","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix-debuginfo","purl":"pkg:rpm/redhat/postfix-debuginfo","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::desktop","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix-pflogsumm","purl":"pkg:rpm/redhat/postfix-pflogsumm","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::es","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix","purl":"pkg:rpm/redhat/postfix","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::es","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix-debuginfo","purl":"pkg:rpm/redhat/postfix-debuginfo","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::es","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix-pflogsumm","purl":"pkg:rpm/redhat/postfix-pflogsumm","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::ws","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix","purl":"pkg:rpm/redhat/postfix","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::ws","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix-debuginfo","purl":"pkg:rpm/redhat/postfix-debuginfo","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:4::ws","fixed":["2:2.2.10-1.5.el4"],"introduced":["0"],"last_affected":[],"package":"postfix-pflogsumm","purl":"pkg:rpm/redhat/postfix-pflogsumm","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:5::server","fixed":["2:2.3.3-2.3.el5_6"],"introduced":["0"],"last_affected":[],"package":"postfix","purl":"pkg:rpm/redhat/postfix","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:5::server","fixed":["2:2.3.3-2.3.el5_6"],"introduced":["0"],"last_affected":[],"package":"postfix-debuginfo","purl":"pkg:rpm/redhat/postfix-debuginfo","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:5::server","fixed":["2:2.3.3-2.3.el5_6"],"introduced":["0"],"last_affected":[],"package":"postfix-pflogsumm","purl":"pkg:rpm/redhat/postfix-pflogsumm","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:6::server","fixed":["2:2.6.6-2.2.el6_1"],"introduced":["0"],"last_affected":[],"package":"postfix","purl":"pkg:rpm/redhat/postfix","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:6::server","fixed":["2:2.6.6-2.2.el6_1"],"introduced":["0"],"last_affected":[],"package":"postfix-debuginfo","purl":"pkg:rpm/redhat/postfix-debuginfo","source":"RHSA-2011:0843"},{"ecosystem":"Red Hat:enterprise_linux:6::server","fixed":["2:2.6.6-2.2.el6_1"],"introduced":["0"],"last_affected":[],"package":"postfix-perl-scripts","purl":"pkg:rpm/redhat/postfix-perl-scripts","source":"RHSA-2011:0843"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2011-1719"},"products":["n/a"],"published":"2011-05-13","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":"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":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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-06","vendors":["n/a"]},"summary":"Remote attackers can cause denial of service or execute arbitrary code via heap memory corruption in Postfix when specific SASL authentication methods are enabled.","url":"https://insights.sbomify.com/CVE-2011-1720/"}