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
StatusAny
WeaknessMemory Corruption
- 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
11 of 15,219 reports · 227 analysed so far
- #212241Validsprintf combined format string attackRuby · Memory Corruption · 2017–18votes
- #144482ValidStringIO strio_getline() can divulge arbitrary memoryRuby · Memory Corruption · 2016–13votes
- #298246Validcontrolled buffer under-read in pack_unpack_internal()Ruby · Memory Corruption · 2018–12votes
- #209949ValidArbitrary heap exposure in JSON.generateRuby · Memory Corruption · 2017–9votes
- #192127ValidBuffer underflow in sprintfRuby · Memory Corruption · 2017–7votes
- #247640InformativeRuby 2.4.1 has "Stack consistency error" and aborts when processing return statement within a case statementRuby · Memory Corruption · 2017–4votes
- #198927ValidParsing invalid unicode codepoints using json c extension (2.0.1+) triggers a segfaultRuby · Memory Corruption · 2017–4votes
- #235842ValidRuby 2.3.x and 2.2.x still bundle DoS vulnerable verision of libYAMLRuby · Memory Corruption · 2017–3votes
- #144485InformativeHeap corruption in string.c tr_trans() due to undersized bufferRuby · Memory Corruption · 2016–2votes
- #144484InformativeHeap corruption in DateTime.strftime() on 32 bit for certain format stringsRuby · Memory Corruption · 2016–1votes
- #304115InformativeInteger Underflow @ ossl_cipher_pkcs5_keyivgenRuby · Memory Corruption · 2018–0votes
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.