Skip to content

Bug bounty reports15,219

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

Program:Ruby
Status:Valid
Clear
Severity
Weakness
Year:2017
Clear
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters10 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
NET::Ftp allows command injection in filenames#294462ValidCommand and Code Injection–2017-12-19–28
sprintf combined format string attack#212241ValidMemory Corruption–2017-09-22–18
Open S3 Bucket WriteAble To Any Aws User#209223ValidAuthentication–2017-03-29–14
Writable RubyCi Amazon s3 bucket#207053ValidAuthentication–2017-02-27–14
Arbitrary heap exposure in JSON.generate#209949ValidMemory Corruption–2017-09-25–9
public report - Reproducible - Writable RubyCi Amazon s3 bucket[207053]#209251ValidAuthentication–2017-03-29–7
Buffer underflow in sprintf#192127ValidMemory Corruption–2017-03-05–7
Escape sequence injection vulnerability in WEBrick BasicAuth#223363ValidCommand and Code Injection–2017-09-15–5
Parsing invalid unicode codepoints using json c extension (2.0.1+) triggers a segfault#198927ValidMemory Corruption–2017-10-25–4
Ruby 2.3.x and 2.2.x still bundle DoS vulnerable verision of libYAML#235842ValidMemory Corruption–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 (549 analysed so far), which can be wrong. Data as of 2026-11-14.

Updated AboutDevelopersSign in