Bug bounty program

Valve

Platform: HackerOne
Bounties: Pays
Assets in scope: 21
Disclosed reports: 82
Subdomains: 790

Most upvoted reports82

Most upvoted reports of Valve
Report	Weakness	Disclosed	Bounty	Votes
RCE on Steam Client via buffer overflow in Server InfoAnalysed#470520	Memory Corruption	2019-03-15	–	1,289
Getting all the CD keys of any gameAnalysed#391217	Access Control	2018-10-31	$20,000	638
XSS in steam react chat clientAnalysed#409850	Cross-site Scripting	2019-01-07	$7,500	499
Modify in-flight data to payment provider Smart2PayAnalysed#1295844	Input Validation and Logic	2021-08-10	$7,500	443
Panorama UI XSS leads to Remote Code Execution via Kick/Disconnect MessageAnalysed#631956	Command and Code Injection	2019-10-08	–	420
SQL Injection in report_xml.php through countryFilter[] parameterAnalysed#383127	SQL Injection	2018-07-27	$25,000	410
Malformed .BMP file in Counter-Strike 1.6 may cause shellcode injectionAnalysed#397545	Memory Corruption	2020-02-27	–	321
Malformed NAV file leads to buffer overflow and code execution in Left4Dead2.exeAnalysed#542180	Memory Corruption	2020-03-25	$10,000	268
Unchecked weapon id in WeaponList message parser on client leads to RCEAnalysed#513154	Memory Corruption	2019-09-17	$3,000	229
OOB reads in network message handlers leads to RCEAnalysed#807772	Memory Corruption	2021-05-04	$7,500	219

Subdomains790

Root

Scope

Name suggests:API

First seen

Text fileClear filters5 names

Subdomains of Valve
Name	Scope	First seen
api.steamcommunity.comapi	Not in the scope	2026-11-14
api.steampowered.comapi	In scope	2026-11-14
api-beta.steampowered.comapi, staging	Not in the scope	2026-11-14
api.origin.steampowered.comapi	Not in the scope	2026-11-14
api.staging.steampowered.comapi, staging	Not in the scope	2026-11-14

13 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.