{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3349 exists.","fix":"No fix has been published for CVE-2021-3349 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-3349 is a low-severity vulnerability in n/a, published on 1 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-3349 and fix it if it is affected.\n\nWhat it is: CVE-2021-3349 is a low-severity vulnerability in n/a, published on 1 Feb 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3349 exists.\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-3349/ (Markdown: https://insights.sbomify.com/CVE-2021-3349/index.md)","id":"CVE-2021-3349","markdown":"https://insights.sbomify.com/CVE-2021-3349/index.md","name":"CVE-2021-3349","record":{"aliases":["DEBIAN-CVE-2021-3349","GHSA-q5mm-jcp2-mc43"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GNOME Evolution","requires_auth":"low_privilege","summary":"GNOME Evolution incorrectly displays valid signature messages for unknown identifiers on trusted keys, bypassing cryptographic verification.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"evolution","vendor":"gnome"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"GNOME Evolution through 3.38.3 produces a \"Valid signature\" message for an unknown identifier on a previously trusted key because Evolution does not retrieve enough information from the GnuPG API. NOTE: third parties dispute the significance of this issue, and dispute whether Evolution is the best place to change this behavior","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Security feature bypass in n/a","id":"CVE-2021-3349","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-3350"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2021-3348"},"products":["n/a"],"published":"2021-02-01","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-12422","kev_date_added":null,"published":"2018-06-15"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2008-1109","kev_date_added":null,"published":"2008-06-04"},{"cvss_score":7.8,"headline":"Path traversal in ytnef","id":"CVE-2009-3721","kev_date_added":null,"published":"2021-05-26"},{"cvss_score":7.6,"headline":"Memory corruption in n/a","id":"CVE-2008-1108","kev_date_added":null,"published":"2008-06-04"},{"cvss_score":7.5,"headline":"Information disclosure in Evolution","id":"CVE-2013-4166","kev_date_added":null,"published":"2020-02-06"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2005-2549","kev_date_added":null,"published":"2005-08-12"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2005-2550","kev_date_added":null,"published":"2005-08-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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"GNOME Evolution incorrectly displays valid signature messages for unknown identifiers on trusted keys, bypassing cryptographic verification.","url":"https://insights.sbomify.com/CVE-2021-3349/"}