Banner object (1)

Hack and Take the Cash !

756 bounties in database
Verizon Media logo


50 $ 

Verizon Media

Welcome to Verizon Media

With brands like Yahoo, HuffPost and TechCrunch, Verizon Media helps people stay informed and entertained, communicate and transact, while creating new ways for advertisers and partners to connect. With technologies like XR, AI, machine-learning, and 5G, we’re transforming media for tomorrow, too.


We are Paranoid

Our information security team is known as the Paranoids, and we’re committed to protecting our brands and our users. As part of this commitment, we invite security researchers to help protect Verizon Media and its users by proactively identifying security vulnerabilities via our bug bounty program. Our program is inclusive of all Verizon Media brands and offers competitive rewards for a wide array of vulnerabilities. We encourage security researchers looking to participate in our bug bounty program to review our policy to ensure compliance with our rules and also to help you safely verify any vulnerabilities you may uncover.


Table of Contents

  • Rules of Engagement
    1. Program Rules
    2. Legal Terms
    3. Safe Harbor
  • Responsible Disclosure of Vulnerabilities
    1. Testing
    2. Crafting a Report
    3. Program Scope
  • Rewards
    1. Payout Table
    2. Valued Vulnerabilities
    3. Borderline Out-of-Scope, No Bounty
    4. Do Not Report

Rules of Engagement

By submitting reports or otherwise participating in this program, you agree that you have read and will follow the Program Rules and Legal Terms sections of this program Policy.

Program Rules

Violation of any of these rules can result in ineligibility for a bounty and/or removal from the program. Three strikes will earn you a temporary ban. Four strikes means a permanent ban.

  1. Test vulnerabilities only against accounts that you own or accounts that you have permission from the account holder to test against.
  2. Never use a finding to compromise/exfiltrate data or pivot to other systems. Use a proof of concept only to demonstrate an issue.
  3. If sensitive information--such as personal information, credentials, etc.--is accessed as part of a vulnerability, it must not be saved, stored, transferred, accessed, or otherwise processed after initial discovery. All copies of sensitive information must be returned to Verizon Media and may not be retained.
  4. Researchers may not, and are not authorized to engage in any activity that would be disruptive, damaging or harmful to Verizon Media, its brands or its users. This includes: social engineering, phishing, physical security and denial of service attacks against users, employees, or Verizon Media as a whole.
  5. Abide by the program scope. Only reports submitted to this program and against assets in scope will be eligible for monetary award.
  6. Researchers may not publicly disclose vulnerabilities (sharing any details whatsoever with anyone other than authorized Verizon Media or HackerOne employees), or otherwise share vulnerabilities with a third party, without Verizon Media’s express written permission.

Legal Terms

In connection with your participation in this program you agree to comply with Verizon Media’s Terms of Service, Verizon Media’s Privacy Policy, and all applicable laws and regulations, including including any laws or regulations governing privacy or the lawful processing of data.

Verizon Media reserves the right to change or modify the terms of this program at any time. You may not participate in this program if you are a resident or individual located within a country appearing on any U.S. sanctions lists (such as the lists administered by the US Department of the Treasury’s OFAC).

Verizon Media does not give permission/authorization (either implied or explicit) to an individual or group of individuals to (1) extract personal information or content of Verizon Media users or publicize this information on the open, public-facing internet without user consent or (2) modify or corrupt programs or data belonging to Verizon Media in order to extract and publicly disclose data belonging to Verizon Media.

Verizon Media employees (including former employees that separated from Verizon Media within the prior 12 months), contingent workers, contractors and their personnel, and consultants, as well as their immediate family members and persons living in the same household, are not eligible to receive bounties or rewards of any kind under any Verizon Media programs, whether hosted by Verizon Media or any third party.

Safe Harbor

Verizon Media will not initiate a lawsuit or law enforcement investigation against a researcher in response to reporting a vulnerability if the researcher fully complies with this Policy.

Please understand that if your security research involves the networks, systems, information, applications, products, or services of another party (which is not us), that third party may determine whether to pursue legal action. We cannot and do not authorize security research in the name of other entities. If legal action is initiated by a third party against you and you have complied with this Policy, we will take reasonable steps to make it known that your actions were conducted in compliance with this Policy.

You are expected, as always, to comply with all applicable laws and regulations.

Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by this Policy.

Responsible Disclosure of Vulnerabilities

We are continuously working to evolve our bug bounty program. We aim to respond to incoming submissions as quickly as possible and make every effort to have bugs fixed within 90 days of being triaged.

Each brand that is part of Verizon Media is represented in at least one of the programs listed here. Please review the program scope before submitting a report. Private scope is accessible to invited researchers only.


Web traffic to and from Verizon Media properties produces petabytes of data every day. When testing, you can make it easier for us to identify your testing traffic against our normal data and the malicious actors out in the world. Please do one or both of the following when participating in one of the Verizon Media bug bounty programs:

  • Where possible, register accounts using your <username> addresses. Some of our properties will require this to be eligible for bounty.
  • Provide your IP address in the bug report. We will keep this data private and only use it to review logs related to your testing activity.
  • Include a custom HTTP header in all your traffic. Burp and other proxies allow the easy automatic addition of headers to all outbound requests. Report to us what header you set so we can identify it easily. For example:
    • A header that includes your username: X-Bug-Bounty:HackerOne-<username>
    • A header that includes a unique or identifiable flag X-Bug-Bounty:ID-<sha256-flag>

When testing for a bug, please also keep in mind:

  • Only use authorized accounts so as not to inadvertently compromise the privacy of our users
  • When attempting to demonstrate root permissions with the following primitives in a vulnerable process please use the following commands:
    • Read : cat /proc/1/maps
    • Write : touch /root/<your H1 username>
    • Execute : id, hostname, pwd (though, technically cat and touch also prove execution)
  • Minimize the mayhem. Adhere to program rules at all times. Do not use automated scanners/tools - these tools include payloads that could trigger state changes or damage production systems and/or data.
  • Before causing damage or potential damage: Stop, report what you've found and request additional testing permission.

Crafting a Report

If our security team cannot reproduce and verify an issue, a bounty cannot be awarded. To help streamline our intake process, we ask that submissions include:

  • Description of the vulnerability
  • Steps to reproduce the reported vulnerability
  • Proof of exploitability (e.g. screenshot, video)
  • Perceived impact to another user or the organization
  • Proposed CVSSv3 __Vector& Score ( without environmental and temporal modifiers)
  • List of URLs and affected parameters
  • Other vulnerable URLs, additional payloads, Proof-of-Concept code
  • Browser, OS and/or app version used during testing

Note: Failure to adhere to these minimum requirements may result in the loss of a reward.

All supporting evidence and other attachments must be stored only within the report you submit. Do not host any files on external services.

Same Bug, Different Host

For each report, please allow Verizon Media sufficient time to patch other host instances. If you find the same bug on a different (unique) host, prior to the report reaching a triaged state, file it within the existing report to receive an additional 10% bonus (per host, not domain). Any reports filed separately while we are actively working to resolve the issue will be treated as a duplicate.

Same Payload, Different Parameter

In some cases, rewards may be consolidated into a single payout. For example, multiple reports of the same vulnerability across different parameters of a resource, or demonstrations of multiple attack vectors against a fundamental framework issue. We kindly ask you to consolidate reports rather than separate them.

Program Scope

Vulnerabilities on a specific brand or web property should be reported to the program to which it belongs. Please see our detailed scope list at the bottom of this page for a full list of assets that are out of scope. This list is subject to change without notice. To reduce the amount of assets listed in each program we operate, out of scope assets are only listed on our public program policy page.
If you’ve found a vulnerability that affects an asset belonging to Verizon Media, but is not included as in scope on any of the Verizon Media programs, please report it to this program.


You will be eligible for a bounty only if you are the first person to disclose an unknown issue. Qualifying bugs will be rewarded based on severity, to be determined by Verizon Media in its sole discretion. Rewards may range from HackerOne Reputation Points and swag to monetary rewards up to $15,000 USD. Awards are granted entirely at the discretion of Verizon Media.

At Verizon Media's discretion, providing more complete research, proof-of- concept code and detailed write-ups may increase the bounty awarded. Conversely, Verizon Media may pay less for vulnerabilities that require complex or over-complicated interactions or for which the impact or security risk is negligible. Rewards may be denied if there is evidence of program policy violations. A reduction in bounty is also warranted for reports that require specific browser configurations.

Payout Table

Where a monetary bounty is presented, eligible reports will be awarded based on severity after identifying final impact, as determined by Verizon Media.

Severity | Payout Range
Critical | $10,000 - $15,000
High | $3,000 - $10,000
Medium | $500 - $3,000
Low | $0 - $500
None | $0

Valued Vulnerabilities

All reports will be awarded based on the Common Weakness Enumeration classification. This table provides the CWEs that we will accept, the severity ranges we will classify reports within for the CWE, and some examples of common vulnerability and attack names that we classify within each CWE that we will accept. This table serves only as a guide and the severity classification of a particular vulnerability will be determined by Verizon Media in its sole discretion.

Note: Non-listed vulnerabilities may also be eligible. Some vulnerability types may fall under a variety of severity ratings determined by scope/scale of exploitation and impact.

Severity (low) | Severity (high) | CWE-ID | Common Weakness Enumeration | Bug Examples
Critical | Critical | CWE-78 __| OS Command Injection | Remote Code Execution; Code Injection; LDAP Injection
Critical | Critical | CWE-12 __| Classic Buffer Overflow | Buffer Overflow
High | Critical | CWE-89 __| SQL Injection | SQL Injection
High | Critical | CWE-918 __| Server-Side Request Forgery | SSRF
Medium | Critical | CWE-732 __| Incorrect Permission Assignment for Critical Resource | IDOR; Horizontal Privilege Escalation; Vertical Privilege Escalation
Critical | Critical | CWE-91 __| XML Injection | XML Injection
High | Critical | CWE-134 __| Uncontrolled Format String | Insecure Deserialization
High | Critical | CWE-250 __| Execution with Unnecessary Privileges | Privilege Escalation to System Account
Low | Critical | CWE-829 __| Inclusion of Functionality from Untrusted Control Sphere | Server Side Includes Injection; Local File Inclusion; XML External Entity; Directory Traversal
Medium | High | CWE-306 __| Missing Authentication for Critical Function | Exposed Administrative Interface
Medium | Critical | CWE-862 __| Missing Authorization | Horizontal Privilege Escalation; Vertical Privilege Escalation; IDOR
Low | Critical | CWE-200 __| Information Exposure | User Enumeration with PII; Credentials on GitHub
Medium | High | CWE-863 __| Incorrect Authorization | Authorization Bypass; Account Takeover
Medium | High | CWE-798 __| Use of Hard-coded Credentials | Hard Coded Credentials
Medium | High | CWE-434 __| Unrestricted Upload of File with Dangerous Type | Unfiltered File Upload
Low | High | CWE-203 __| Information Exposure Through Discrepancy | PHP Admin Information page; MySQL Information page (w/ credentials); Apache Status page
Medium | Medium | CWE-494 __| Download of Code Without Integrity Check | S3 Bucket Upload
Low | Medium | CWE-311 __| Missing Encryption of Sensitive Data | Cleartext Submission of Passwords
Low | Medium | CWE-807 __| Reliance on Untrusted Inputs in a Security Decision |
Low | Medium | CWE-79 __| Cross-Site Scripting | Stored XSS; POST-Based XSS; GET-Based XSS; DOM-Based XSS; Flash-based XSS; CSS Injection
Medium | Medium | CWE-352 __| Cross-Site Request Forgery | State-Changing CSRF; Non-State-Changing CSRF
Low | Medium | CWE-16 __| Misconfiguration | Subdomain Takeover; Dangling DNS Record
Medium | Medium | CWE-93 __| CRLF Injection | CRLF Injection
Low | Low | CWE-601 __| Open Redirect | Open Redirect
Informative | Low | CWE-327 __| Use of a Broken or Risky Cryptographic Algorithm | Weak CAPTCHA
Informative | Low | CWE-307 __| Improper Restriction of Excessive Authentication Attempts | Lack of Rate Limiting on Login; CAPTCHA Bypass

Borderline Out-of-Scope, No Bounty

These issues are eligible for submission, but not eligible for bounty or any award. Once triaged, they will be closed as Informative only if found to be valid orSpam if found to be not valid. When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.

Any non-Verizon Media Applications | "Self" XSS
Missing Security Best Practices | HTTP Host Header XSS
Confidential Information Leakage | Clickjacking/UI Redressing
Use of known-vulnerable library (without proof of exploitability) | Intentional Open Redirects
Missing cookie flags | Reflected file download
SSL/TLS Best Practices | Incomplete/Missing SPF/DKIM
Physical attacks | Social Engineering attacks
Results of automated scanners | Login/Logout/Unauthenticated CSRF
Autocomplete attribute on web forms | Using unreported vulnerabilities
"Self" exploitation | Issues related to networking protocols
XSS in flash files not developed by Verizon Media (e.g. Camtasia, JW Player, Flowplayer swf files) | Software Version Disclosure
Verbose error pages (without proof of exploitability) | Denial of Service attacks
Verizon Media software that is End of Life or no longer supported | Account/email Enumeration
Missing Security HTTP Headers (without proof of exploitability) | Internal pivoting, scanning, exploiting, or exfiltrating data

Note: 0-day vulnerabilities may be reported 30 days after initial publication. We have a team dedicated to tracking these issues; hosts identified by this team and internally ticketed will not be eligible for bounty.

Do Not Report

The following issues are considered out of scope:

  • Those that resolve to third-party services
  • Issues that do not affect the latest version of modern browsers
  • Issues that we are already aware of or have been previously reported
  • Issues that require unlikely user interaction
  • Disclosure of information that does not present a significant risk
  • Cross-site Request Forgery with minimal security impact
  • CSV injection
  • Incomplete or missing SPF/DKIM
  • General best practice concerns

Hall of Fame

List your Bug Bounty for free immediately!

Contact us if you want more information.

FireBounty (c) 2015-2019