Abercrombie & Fitch Bug Bounty

Abercrombie & Fitch Management Co. (ANF) looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted consistently with this policy, we will take steps to make it known that your actions were authorized.

Disclosure Policy

• Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express written consent from Abercrombie & Fitch Management Co.
• Follow HackerOne's disclosure guidelines.

Program Rules

Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.

• We are continuously scanning our applications for vulnerabilities. Abercrombie & Fitch will operate in good faith to pay out net new vulnerabilities disclosed through this program. Findings related to newly released CVEs will be evaluated against Abercrombie & Fitch’s existing vulnerability management processes. Cases in which the vulnerability has already been triaged and slated for remediation within SLAs will be treated as a duplicate findings.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact. Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
• When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
• If using a publicly available POC / exploit, please provide the source. This helps ANF understand risk, impact and remediate. Leveraging public POCs will not result in reduced bounty. Providing sources of lesser-known successful exploits may result in a bonus reward.
• Exfiltration and/or exposure of personally identifiable information is expressly prohibited. If you believe a vulnerability exists where PII may be exposed, please ensure you are using your own test accounts for POC.
• If submitting a ticket regarding found system credentials, researchers must provide the source. Credentials must not be used to access underlying systems. Tickets will be evaluated and assigned a value at ANF's discretion based on the class of identity and its level of access.
• Social engineering (e.g. phishing, vishing, smishing) including interactions with customer service or chat agents is prohibited.
• Emailing the Abercrombie security team or any other associates directly is prohibited. All communications must be via the Hackerone platform.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own.
• A&F corporate employees, contractors (past and current), and connected entities are not eligible for participation in this program.
• Abercrombie’s and Hollister Co.’s underlying architecture is the same. The same rule can be applied to exposed non-prod environments if found. Refrain from submitting a duplicate report for the other domain or environment.

Test Plan

• We strongly recommend the use of a modified a user agent in your HTTP(S) requests, and for non-HTTP requests we strongly recommend you add an identification to artifacts in POCs, and, or payloads so our teams can identify you as a verified researcher and not a malicious attacker: (e.g. h1:<bbp-hackeroneusername>).
• No credentials are required or provided for this program. If you self-register for any accounts, please register with your @wearehackerone.com email address. You may not use exposed credentials to continue testing without explicit written approval of Abercrombie & Fitch Management Co.

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• Clickjacking on pages with no sensitive actions
• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
• Cross-Site Scripting (XSS/RXSS)
• Attacks requiring MITM or physical access to a user's device.
• Previously known vulnerable libraries without a working Proof of Concept.
• Comma Separated Values (CSV) injection without demonstrating a vulnerability.
• Missing best practices in SSL/TLS configuration.
• Any activity that could lead to the disruption of our service (DoS).
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• Rate limiting, bruteforce or enumeration issues on non-authentication endpoints
• Missing best practices in Content Security Policy.
• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors) without PoC are considered informational.
• Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
• Tabnabbing and typosquatting
• Open redirect - unless an additional security impact can be demonstrated
• Issues that require unlikely user interaction, including but not limited to phishing.
• Promotional code abuse
• Social Engineering of customer service agents via voice or chat

Response Targets

Abercrombie & Fitch Management Co. will make a best effort to meet the following SLAs for hackers participating in our program:

SLA in business days

We’ll try to keep you informed about our progress throughout the process.

Thank you for helping keep Abercrombie & Fitch Management Co. and our users safe!