Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program:Tor
Status
Severity:High
Clear
Weakness
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account1
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Technique
Clear filters9 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Tor Browser: iframe with `data:` uri has access to parent window#358005InformativeNo weakness recordedHigh2018-06-06––
Stack overflow in UnbindFromTree (browser can be crashed remotely)#264481InformativeMemory CorruptionHigh2017-10-02–1
Information Exposure Through Directory Listing#1316412N/AInformation DisclosureHigh2021-08-27–3
Tor Browser using --log or --verbose logs the exact connection time a client connects to any v2 domains.#1250273InformativeInformation DisclosureHigh2021-09-27–4
[Android org.torproject.android] Possible to force list of bridges#252626InformativeAccess ControlHigh2017-08-21–13
Address Bar Spoofing on TOR Browser#275960InformativeInput Validation and LogicHigh2023-01-02–14
Access to local file system using javascript#258630ValidMisconfiguration and Insecure DesignHigh2017-11-18–15
De-anonymization by visiting specially crafted bookmark.#294364ValidInformation DisclosureHigh2018-07-03–15
Snowflake server: Leak of TLS packets from other clientsAnalysed#1880610ValidInformation DisclosureHigh2023-03-15–30

Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (4,365 analysed so far), which can be wrong. Data as of 2026-11-15.