{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-24661 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-24661 is a medium-severity vulnerability in Fedoraproject Fedora, published on 26 Aug 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-24661 and fix it if it is affected.\n\nWhat it is: CVE-2020-24661 is a medium-severity vulnerability in Fedoraproject Fedora, published on 26 Aug 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-24661 in the wild and no public exploit code.\n\nAffected product: Fedoraproject Fedora. 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-24661/ (Markdown: https://insights.sbomify.com/CVE-2020-24661/index.md)","id":"CVE-2020-24661","markdown":"https://insights.sbomify.com/CVE-2020-24661/index.md","name":"CVE-2020-24661","record":{"aliases":["CLEANSTART-2023-LD05714","DEBIAN-CVE-2020-24661","GHSA-9q4r-jrvx-7p2q","MGASA-2020-0390","UBUNTU-CVE-2020-24661","openSUSE-SU-2024:10781-1"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Geary email client","requires_auth":"none","summary":"Geary email client fails to verify pinned TLS certificates in specific configurations, allowing attackers to intercept mail via man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fedora","vendor":"fedoraproject"},{"product":"geary","vendor":"gnome"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"GNOME Geary before 3.36.3 mishandles pinned TLS certificate verification for IMAP and SMTP services using invalid TLS certificates (e.g., self-signed certificates) when the client system is not configured to use a system-provided PKCS#11 store. This allows a meddler in the middle to present a different invalid certificate to intercept incoming and outgoing mail.","ecosystems":["openSUSE:Tumbleweed"],"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":"Security feature bypass in n/a","id":"CVE-2020-24661","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fedoraproject:fedora","products":["fedoraproject:fedora"],"type":"security_feature_bypass","year":"2020"},"n_packages":1,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-24662"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["40.0-1.4"],"introduced":["0"],"last_affected":[],"package":"geary","purl":"pkg:rpm/opensuse/geary\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:10781-1"}],"prev":{"headline":"Lack of URL normalization may lead to authorization bypass when URL access rules are used","id":"CVE-2020-24660"},"products":["n/a"],"published":"2020-08-26","related":[{"cvss_score":9.8,"headline":"PHP-CGI OS Command Injection","id":"CVE-2024-4577","kev_date_added":"2024-06-12","published":"2024-06-09"},{"cvss_score":9.8,"headline":"Grafana Authentication Bypass","id":"CVE-2021-39226","kev_date_added":"2022-08-25","published":"2021-10-05"},{"cvss_score":9.8,"headline":"VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow","id":"CVE-2019-5544","kev_date_added":"2021-11-03","published":"2019-12-06"},{"cvss_score":9.6,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2024-4947","kev_date_added":"2024-05-20","published":"2024-05-15"},{"cvss_score":9.6,"headline":"Google Chromium Visuals Use-After-Free","id":"CVE-2024-4671","kev_date_added":"2024-05-13","published":"2024-05-09"},{"cvss_score":9.6,"headline":"Google Chromium Mojo Insufficient Data Validation","id":"CVE-2022-3075","kev_date_added":"2022-09-08","published":"2022-09-26"},{"cvss_score":9.6,"headline":"Google Chromium Indexed DB API Use-After-Free","id":"CVE-2021-30633","kev_date_added":"2021-11-03","published":"2021-10-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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-04","vendors":["n/a"]},"summary":"Geary email client fails to verify pinned TLS certificates in specific configurations, allowing attackers to intercept mail via man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2020-24661/"}