Western Union is a financial services and communications company based in the United States.
In general, Western Union adheres to the Bugcrowd Vulnerability Rating Taxonomy for the prioritization of findings, but they do reserve the right to alter priority on a case-by-case basis. Any submission where the priority is altered will be accompanied by an explanation from the Western Union team.
Out of scope
Additional Information/Rules of Engagement:
- Assets in the scope above are variations on a core web application handling all requests, as such, security issues reproduced in one domain will be reproducible in other domains, making them a single core issue and only worth a single reward.
- Submissions of a P1-P2 rating must include a working proof of concept to be eligible for a reward.
10/5/18 - JSON, JS and CSS will not be rewarded or marked as out of scope. Reflected XSS will be marked as p4 and stored XSS as P3.
5/24/18 - both www.speedpay.com payments.westernunion.com are now in-scope targets for the program.
7/10/18 - wuagentportal.westernunion.com, agentportal.westernunion.com, and paynow7.speedpay.com are now in-scope targets for the program.
- Send Money / Track Transfer pages
- We are most interested in vulnerabilities on our core platform and infrastructure
- Ability to remotely gain access to other user's PCI Details (Credit card, CVV, etc)
- Ability to remotely gain access to other user's PII Details (First name, last name ,payment information’s , etc)
Out of Scope
- Do not perform DoS or DDoS attacks.
- Do not in any way attack our end users, or engage in the trade of stolen/breached user credentials.
- Do NOT conduct non-technical attacks such as social engineering, phishing or unauthorized access to Infrastructure.
- Do NOT use automated scanners and tools.
The following finding types are specifically excluded from the bounty:
- 3rd Party Clients (e.g. WordPress). If you are unsure whether or not a client is 3rd party, please check with us.
- Re-posting of vendor notices for platform updates
- Descriptive error messages (e.g. Stack Traces, application or server errors).
- Login Page / Forgot Password Page Account Brute force or account lockout not enforced.
- HTTP 404 codes/pages or other HTTP non-200 codes/pages.
- Banner disclosure on common/public services.
- Disclosure of known public files or directories, (e.g. robots.txt).
- Clickjacking and issues only exploitable through clickjacking.
- Self-XSS and issues exploitable only through Self-XSS.
- CSRF on forms that are available to anonymous users (e.g. the contact form).
- Logout Cross-Site Request Forgery (logout CSRF).
- Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality.
- Findings derived from SSL settings (e.g. BREACH attack, insecure SSL ciphers enabled).
- Lack of Secure and HTTPOnly cookie flags.
- Lack of Security Speedbump when leaving the site.
- Username Enumeration
- Visible Detailed Error/Debug Page - Detailed Server Configuration