Security readout for executives and security teams
Plain-English summary
This issue could cause Brave Desktop to leak some DNS lookups outside a proxy under a specific configuration. The business impact is privacy exposure: browsing-related domain lookups may be visible to the system DNS path instead of staying within the intended proxy controls.
Executive priority
Treat this as a targeted privacy-control failure rather than a broad compromise event. Prioritize users who rely on proxying for confidentiality, anonymity, or regulated browsing segregation.
Technical view
Brave Desktop 1.17 through 1.33 before 1.33.106 could issue additional DNS requests outside a proxying extension when CNAME-based adblocking and a proxying extension with SOCKS fallback were enabled. The CVE notes this resulted from an incomplete fix for CVE-2021-21323 and CVE-2021-22916.
Likely exposure
Exposure appears limited to Brave Desktop versions before 1.33.106 in the 1.17-1.33 range, with CNAME-based adblocking and a SOCKS-fallback proxying extension enabled. The supplied sources do not identify server-side exposure, other Brave products, or broader default exposure.
Exploitation context
The provided sources describe information disclosure through DNS leakage. They do not provide evidence of active exploitation, and the CVE is not listed as KEV in the supplied bundle.
Researcher notes
The key condition is the interaction between CNAME-based adblocking and proxy extension fallback behavior. Evidence in the bundle does not include CVSS, CWE, exploit status, or detailed remediation beyond the fixed version boundary.
Mitigation direction
- Upgrade Brave Desktop to 1.33.106 or later.
- Check Brave vendor guidance for any additional configuration recommendations.
- Avoid the affected proxy-extension and CNAME-adblocking combination until updated.
- Review privacy-sensitive users who depended on proxy-enforced DNS isolation.
Validation and detection
- Inventory Brave Desktop versions across managed endpoints.
- Confirm whether affected endpoints use proxying extensions with SOCKS fallback.
- Check whether CNAME-based adblocking was enabled on those endpoints.
- Validate upgraded systems no longer match the affected version range.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-45884 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/brave/brave-core/pull/10742CVE reference · x_refsource_MISC
- https://github.com/brave/brave-browser/issues/19070CVE reference · x_refsource_MISC
- https://github.com/brave/brave-browser/issues/20079CVE reference · x_refsource_MISC
- https://hackerone.com/reports/1377864CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.