{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8276 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8276 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8276 is a medium-severity vulnerability in https://github.com/brave/brave-core, published on 9 Nov 2020. 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-2020-8276 and fix it if it is affected.\n\nWhat it is: CVE-2020-8276 is a medium-severity vulnerability in https://github.com/brave/brave-core, published on 9 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-8276 in the wild and no public exploit code.\n\nAffected product: https://github.com/brave/brave-core. 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-8276/ (Markdown: https://insights.sbomify.com/CVE-2020-8276/index.md)","id":"CVE-2020-8276","markdown":"https://insights.sbomify.com/CVE-2020-8276/index.md","name":"CVE-2020-8276","record":{"aliases":["GHSA-v36p-6rf8-wx94"],"analysis":{"component_type":"browser","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Brave Desktop Browser","requires_auth":"low_privilege","summary":"Brave Desktop logged timestamps for Tor incognito windows locally, potentially revealing usage patterns to attackers with disk access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"brave","vendor":"brave"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"The implementation of Brave Desktop's privacy-preserving analytics system (P3A) between 1.1 and 1.18.35 logged the timestamp of when the user last opened an incognito window, including Tor windows. The intended behavior was to log the timestamp for incognito windows excluding Tor windows. Note that if a user has P3A enabled, the timestamp is not sent to Brave's server, but rather a value from:Used in last 24hUsed in last week but not 24hUsed in last 28 days but not weekEver used but not in last 28 daysNever usedThe privacy risk is low because a local attacker with disk access cannot tell if the timestamp corresponds to a Tor window or a non-Tor incognito window.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in https://github.com/brave/brave-core","id":"CVE-2020-8276","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Uncontrolled Resource Consumption in node","id":"CVE-2020-8277"},"packages":[],"prev":{"headline":"Missing authorization in Citrix Secure Mail for Android","id":"CVE-2020-8275"},"products":["https://github.com/brave/brave-core"],"published":"2020-11-09","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-45884","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2022-47932","kev_date_added":null,"published":"2022-12-24"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2022-47933","kev_date_added":null,"published":"2022-12-24"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2022-47934","kev_date_added":null,"published":"2022-12-24"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2018-10798","kev_date_added":null,"published":"2018-05-07"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2018-10799","kev_date_added":null,"published":"2018-05-07"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2017-8458","kev_date_added":null,"published":"2017-05-03"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Brave Desktop logged timestamps for Tor incognito windows locally, potentially revealing usage patterns to attackers with disk access.","url":"https://insights.sbomify.com/CVE-2020-8276/"}