By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Intigriti Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

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 may 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. Use your own Accounts: Test vulnerabilities only against accounts that you own or accounts that you have written permission from the account holder to test against.

2. Do not pivot: Never use a finding to compromise/exfiltrate data or pivot to other systems. Use a proof of concept only to demonstrate an issue.

3. Respect the Users: 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 Yahoo and may not be retained. To ensure you are fully protected under the 'Safe Harbor', you may only use potentially-sensitive data to validate your finding, report it to us and to verify if the applied fix is effective.

4. Respect the Company: Researchers may not, and are not authorized to, engage in any activity that would be disruptive, damaging or harmful to Yahoo, its brands or its users. This includes: social engineering, phishing, physical security and denial of service attacks against users, employees, or Yahoo as a whole.

5. Follow the Scope: Abide by the program scope. Only reports submitted to this program and against assets in scope will be eligible for monetary award.

6. Get written permission before disclosure: Researchers may not publicly disclose vulnerabilities (sharing any details whatsoever with anyone other than authorized Yahoo or our authorized Bug Bounty Platform employees), or otherwise share vulnerabilities with a third party, without Yahoo’s express written permission.

Legal Terms

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

Yahoo 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).

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

Yahoo employees (including former employees that separated from Yahoo 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 Yahoo programs, whether hosted by Yahoo or any third party.

Safe Harbor

Yahoo 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.

Please review the program scope before submitting a report.

Testing

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

● Where possible, register accounts using your <username>+x@intigriti.me addresses. Some of our properties may require this to be eligible for a bounty.
● Provide your IP address(es) in the bug report. We will keep this data private and only use it to review logs related to your testing activity.
● Limit your requests to 50 requests per second unless otherwise specified in the Scope. Exceeding this rate may result in your traffic becoming blocked.
● Include custom header(s) in all your traffic. Burp Suite, other proxies, and most popular bug hunting tools allow the easy, automatic addition of headers to all outbound requests. Include the header you set so we can identify it easily. This information may be required for the report to be eligible for a bounty.

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

● 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 Intigriti username>
○ Execute: id, hostname, pwd (though, technically cat and touch also prove execution)
● Before potentially causing damage: Stop, report what you've found and request additional testing permission.
● Minimize the mayhem. Adhere to program rules at all times.

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.1 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 no bounty.

All supporting evidence and other attachments must be stored only within the report you submit. Attach all evidence to the report through the Platform. You may NEVER host any files on external services (youtube, dropbox, s3 bucket, self-hosted, etc).

Ceasefire Conditions

Hackers participating in the Yahoo Bug Bounty program may find bugs that require special handling and/or an immediate halt to testing. In these instances, the team will post a message to the primary report related to the identified issue or issue class stating that a Ceasefire is now in effect. A Ceasefire creates a time-bound fix window that allows our engineers to analyze, understand, and address the issue at scale. During this period, Hackers may not continue working on or with the bugs that prompted the halt of testing.

Each Ceasefire will include a blackout period during which additional reports will not be accepted by the program. This period is typically 90 days, depending on the severity of the finding.

Achieving a Ceasefire Condition will result in a bonus to your report. Yahoo does not publish a list of past or current Ceasefire Conditions.

Program Scope

Wherever possible, vulnerabilities should be reported under the correct, in-scope “Asset”. Please see our detailed scope list at the bottom of this page for a full list of assets that are in scope of this program. This list is subject to change without notice.

If you’ve found a vulnerability that affects a Yahoo asset which is not listed as in-scope, please report it to this program; your finding may be eligible for a bounty.

Rewards

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 Yahoo. Rewards may range from Reputation Points and/or swag to monetary rewards up to $15,000 USD. Providing more complete research, proof-of-concept code and detailed write-ups may increase the bounty awarded. Conversely, Yahoo 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 may be warranted for reports that require specific browser configurations. Reports in third party software may not be eligible for bounties; Products or sites developed on behalf of Yahoo may qualify for a 50% bounty. (See scope section for more details)

Bounties and bonuses are granted entirely at the discretion of Yahoo.

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 Yahoo and its users by proactively identifying security vulnerabilities via our bug bounty program. Our program is inclusive of all Yahoo 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.

Full Bounty Table

Click here to discover how we lead the way in crowd-sourced security

Review our Github Repository here

Check out our last Intigriti Live Hacking Event here

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:
Program feedback link
Please note this form will be checked periodically and should not be used for submission or support queries.

The following issues are considered out of scope:

● Assets 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
● CSV injection without security impact

List of Domains and Products not in scope for the Bug Bounty program

SSP Advertising Platforms

These products (listed domains) and any related domains are NOT eligible for bounty or reputation

• CRS - crs-prd.aws.oath.cloud
• Deals UI - deals.o2.verizonmedia.com
• O2 - adaptv.advertising.com
• OneAdServer - console.oneadserver.aol.com
• OneAPI - oneapi.aol.com
• OneCreative - onecreative.aol.com
• OneInsights - alephd.com
• OneMobile - onemobile.aol.com
• OneReporting - vidible.tv
• OneVideo - onevideo.aol.com
• SSP - ssp.verizonmedia.com
• SSP External API - ext.api.ssp.aol.com
• Store - store.vzbuilders.com, sales.oath.com

List of products and companies which were previously owned but have been shut down or sold and are not in scope of Yahoo.

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 Yahoo at 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.

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 if found to be valid or Spam if found to be not valid. When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.

Note: 0-day and other CVE vulnerabilities may be reported 30 days after initial publication (CVE List Status of Published). We have a team dedicated to tracking CVEs as they are released; hosts identified by this team and internally ticketed will not be eligible for bounty.

Special Situations

Some situations exist that may earn partial bounties or bonuses on top of a base bounty per report. Here are a few of the most common examples:

Same Bug, Different Host
For each report, please allow Yahoo 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 5% 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 Bug, Different Path
For each report, please allow Yahoo sufficient time to patch related paths. If you find the same bug on a different (unique) path, prior to the report reaching a triaged state, file it within the existing report to receive an additional 5% bonus (per path). 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.

Note: Additional payloads, parameters, hosts and paths will not receive multiple bonuses.

Where can we get credentials for the app?

Most of our applications allow self register. For any applications that do not support self register, we do not provide test credentials.

Is there an SSRF sheriff?

If you think you've got an SSRF attack against our network, please use these two groups of servers to prove it to us. There's a whole bunch of different file formats on these servers and they're all identical. To prove your SSRF, please send your attacks in a way that attempt to read or write content to/from one of these servers in each network segment (Prod + Corp). The difference between each host within each category is just their geolocation, which in most circumstances does not matter what you target. HTTPS is also enabled on these servers.

Production Network

Corporate Network

Files to target take the filename format of <extension>_###.<extension>. For example: txt_001.txt and zip_001.zip. We've put up a bunch of different file formats that can be targeted for your testing needs. There is one other file that is simple text, but does not have a file extension, reach that by asking for noext_01.

File types available include:
avi, bmp, css, csv, doc, docx, dtd, flv, gif, html, icns, ics, ico, jar, jpg, js, json, md, mkv, mov, mp3, mp4, odp, ods, odt, ogg, pdf, php, png, ppt, rss, svg, tiff, txt, wav, wmv, xls, xlsx, xml, xsl, zip

We’ve also set the 404 error page to show you that you’ve hit the bananastand and not just some other unknown host: <html>...404 no bananas for you!...</html>

When testing, it would be super helpful if (along with the file you pull down) you try to fetch http://<hostname>/intigriti-<username> so that we can identify your activity in the logs more easily.

When submitting a report (in addition to all the usual details) please make sure to:

1. Attach a copy of the file you fetched.
2. Include the timestamp you fetched the file.
3. Note the SSRF server that you fetched the file from.

The Fine Print

If you can’t hit these servers but can hit something else inside our network, you must provide a working POC and understand that we will individually evaluate impact of the host you tested with.

We reserve the right to award a $0 bounty for any SSRF (or similar) reports that are not able to touch these servers.

Also, we will periodically review the logs on these servers and may reach out to hackers that have hit the server but not submitted a report. If this happens, you will be eligible for a maximum award of 10% for the report.