Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| sprintf combined format string attackAnalysed#212241 | Valid | Memory Corruption | Medium | 2017-09-22 | – | 18 |
| Arbitrary heap exposure in JSON.generate#209949 | Valid | Memory Corruption | – | 2017-09-25 | – | 9 |
| Buffer underflow in sprintf#192127 | Valid | Memory Corruption | – | 2017-03-05 | – | 7 |
| Ruby 2.4.1 has "Stack consistency error" and aborts when processing return statement within a case statement#247640 | Informative | Memory Corruption | – | 2017-09-24 | – | 4 |
| Parsing invalid unicode codepoints using json c extension (2.0.1+) triggers a segfault#198927 | Valid | Memory Corruption | None | 2017-10-25 | – | 4 |
| Ruby 2.3.x and 2.2.x still bundle DoS vulnerable verision of libYAML#235842 | Valid | Memory Corruption | Medium | 2017-10-25 | – | 3 |
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, where there is one, which can be wrong. Data as of 2026-11-15.