{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-24721 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24721 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24721 is a medium-severity vulnerability in n/a, published on 30 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-24721 and fix it if it is affected.\n\nWhat it is: CVE-2020-24721 is a medium-severity vulnerability in n/a, published on 30 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-24721 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-24721/ (Markdown: https://insights.sbomify.com/CVE-2020-24721/index.md)","id":"CVE-2020-24721","markdown":"https://insights.sbomify.com/CVE-2020-24721/index.md","name":"CVE-2020-24721","record":{"aliases":["GHSA-9pjj-6grx-8qjx"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Exposure Notifications protocol","requires_auth":"low_privilege","summary":"The GAEN protocol allows attackers to coerce users into revealing their exposure notification status due to persistent private framework state.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exposure_notifications","vendor":"apple"},{"product":"exposure_notifications","vendor":"google"}],"cvss":{"score":5.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[],"description":"An issue was discovered in the GAEN (aka Google/Apple Exposure Notifications) protocol through 2020-09-29, as used in COVID-19 applications on Android and iOS. It allows a user to be put in a position where he or she can be coerced into proving or disproving an exposure notification, because of the persistent state of a private framework.","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":"Information disclosure in n/a","id":"CVE-2020-24721","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Other in n/a","id":"CVE-2020-24722"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-24719"},"products":["n/a"],"published":"2020-09-30","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":"The GAEN protocol allows attackers to coerce users into revealing their exposure notification status due to persistent private framework state.","url":"https://insights.sbomify.com/CVE-2020-24721/"}