Intel · bug bounty
Disclosed bug bounty reports
Every publicly disclosed report on HackerOne the Atlas holds: HackerOne's own outcome, severity, the weakness as filed and the access the title states, and, for analysed reports, how the bug was found in our words.
SortMost upvoted
WeaknessInformation Disclosure
- Any class
- Cross-site Scripting4
- Open Redirect2
- Command and Code Injection11
- Injection and Smuggling5
- Deserialization and Object Injection1
- File and Path Handling2
- Memory Corruption11
- Denial of Service6
- Input Validation and Logic1
- Misconfiguration and Insecure Design1
- Cryptography3
- Information Disclosure4
- Authentication3
- Access Control3
- No weakness recorded16
4 of 15,219 reports · 161 analysed so far
- #166661ValidArbitrary heap overread in strscan on 32 bit Ruby, patch includedRuby · Information Disclosure · 2016–17votes
- #1145454Validlib/net/ftp.rb: trusting PASV responses allow client abuseRuby · Information Disclosure · 2021–9votes
- #778931N/ASource code disclosed via S3 BucketRuby · Information Disclosure · 2020–4votes
- #257276N/AOpen aws s3 bucket s3://rubyciRuby · Information Disclosure · 2017–1votes
The status is HackerOne's own outcome. “Access (title)” is what the report's title states; “Access (analysis)” and techniques come from CyberSIXT's own analysis, a model's summary of the public report that may be wrong. Data as of 2026-11-14.