Tor browsing-time disclosure via persistent warning logs
Published Aug 31, 2021 · Updated Aug 3, 2024
Information disclosure in Brave Browser Desktop before 1.28.62 allows local users to infer Tor browsing times from tor.log. Brave writes Tor control-channel warnings for V2 onion connections, including timestamps, to the on-disk tor.log file. Local access to the user's profile is required; correlation with external connection records reveals when V2 onion sites were visited.
Summary
What happened
Information disclosure in Brave Browser Desktop before 1.28.62 allows local users to infer Tor browsing times from tor.log. Brave writes Tor control-channel warnings for V2 onion connections, including timestamps, to the on-disk tor.log file. Local access to the user's profile is required; correlation with external connection records reveals when V2 onion sites were visited.
The record
- CVE
- CVE-2021-22929
- Published
- Aug 31, 2021
- Updated
- Aug 3, 2024
- Vendor
- Brave
- Product
- Brave Browser
- Classifications
- CWE-532, CWE-312, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 31, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.28.62
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- V2 onion tor.log reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo