Security readout for executives and security teams
Plain-English summary
Brave Browser Desktop before 1.28.62 could write Tor-related warning logs that revealed timestamps for connections to V2 onion domains. This is mainly a privacy and metadata exposure issue: someone with access to the affected log file could infer when onion-domain activity occurred.
Executive priority
Treat as a targeted privacy cleanup rather than an emergency outage risk. Prioritize managed endpoints where Tor usage, sensitive investigations, journalism, legal work, or regulated privacy concerns make activity metadata especially sensitive.
Technical view
The issue is classified as CWE-312, cleartext storage of sensitive information. The described exposure is in Brave Desktop tor.log warning messages, which included connection timestamps for V2 onion domains before version 1.28.62. No CVSS vector is provided in the source bundle.
Likely exposure
Exposure is most relevant where Brave Desktop with Tor functionality was used before version 1.28.62 and local logs could be accessed by administrators, forensic tools, malware, shared users, or backups.
Exploitation context
The supplied sources do not state active exploitation, and the CVE is not listed as KEV in the bundle. This appears to require access to local log data rather than remote code execution.
Researcher notes
Evidence is limited: the bundle provides a short CVE description, CWE-312, no CVSS score, and one HackerOne reference. The affected-version metadata is sparse, but the description clearly says Brave Desktop prior to 1.28.62.
Mitigation direction
- Upgrade Brave Browser Desktop to version 1.28.62 or later.
- Check Brave vendor guidance and the HackerOne report for any additional handling advice.
- Restrict access to browser profile and log locations on managed endpoints.
- Consider log retention review where Tor activity privacy is business-sensitive.
Validation and detection
- Inventory Brave Browser Desktop versions across managed endpoints.
- Identify systems that ran Brave Desktop before version 1.28.62.
- Check whether tor.log exists on affected systems and review privacy exposure risk.
- Confirm updated installations no longer retain vulnerable logging behavior.
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.
CWE-312: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-22929 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://hackerone.com/reports/1249056CVE 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.
Cleartext Storage of Sensitive Information
Cleartext Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.