{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-34814 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-34814 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-34814 is a high-severity vulnerability in n/a, published on 13 Oct 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-34814 and fix it if it is affected.\n\nWhat it is: CVE-2021-34814 is a high-severity vulnerability in n/a, published on 13 Oct 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-34814 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-2021-34814/ (Markdown: https://insights.sbomify.com/CVE-2021-34814/index.md)","id":"CVE-2021-34814","markdown":"https://insights.sbomify.com/CVE-2021-34814/index.md","name":"CVE-2021-34814","record":{"aliases":["GHSA-969f-xmp4-3wpw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Spam Engine","requires_auth":"none","summary":"Attackers can bypass security controls in Proofpoint Spam Engine, potentially allowing malicious content to pass through filtering.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"spam_engine","vendor":"proofpoint"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"Proofpoint Spam Engine before 8.12.0-2106240000 has a Security Control Bypass.","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-2021-34814","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-34815"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-34813"},"products":["n/a"],"published":"2021-10-13","related":[],"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 security controls in Proofpoint Spam Engine, potentially allowing malicious content to pass through filtering.","url":"https://insights.sbomify.com/CVE-2021-34814/"}