{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21323 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-21323 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-21323 is a medium-severity vulnerability in brave-browser, published on 23 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-21323 and fix it if it is affected.\n\nWhat it is: CVE-2021-21323 is a medium-severity vulnerability in brave-browser, published on 23 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-21323 in the wild and no public exploit code.\n\nAffected product: brave-browser. 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-21323/ (Markdown: https://insights.sbomify.com/CVE-2021-21323/index.md)","id":"CVE-2021-21323","markdown":"https://insights.sbomify.com/CVE-2021-21323/index.md","name":"CVE-2021-21323","record":{"aliases":["GHSA-mqjf-9x5g-2rv6"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Brave browser","requires_auth":"none","summary":"Brave browser users with adblocking enabled leak DNS requests from Tor windows, exposing browsing activity to DNS providers.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"brave","vendor":"brave"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Brave is an open source web browser with a focus on privacy and security. In Brave versions 1.17.73-1.20.103, the CNAME adblocking feature added in Brave 1.17.73 accidentally initiated DNS requests that bypassed the Brave Tor proxy. Users with adblocking enabled would leak DNS requests from Tor windows to their DNS provider. (DNS requests that were not initiated by CNAME adblocking would go through Tor as expected.) This is fixed in Brave version 1.20.108","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":"Regression in DNS leakage from Tor windows","id":"CVE-2021-21323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":5,"next":{"headline":"Insecure Direct Object Reference (IDOR) on \"Solutions\"","id":"CVE-2021-21324"},"packages":[],"prev":{"headline":"Prefix escape","id":"CVE-2021-21322"},"products":["brave-browser"],"published":"2021-02-23","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-03","vendors":["brave"]},"summary":"Brave browser users with adblocking enabled leak DNS requests from Tor windows, exposing browsing activity to DNS providers.","url":"https://insights.sbomify.com/CVE-2021-21323/"}