For this program, we're inviting researchers test our freelancer platform, and mobile iOS/Android/Desktop apps. Our goal with this program, is to ensure that our customers are using a secure platform that's free of security vulnerabilities. For the purposes of testing, researchers can create their own user credentials.
For the initial prioritization/rating of findings (with a few exceptions), this program will use the Bugcrowd Vulnerability Rating Taxonomy. However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, a full, detailed explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.
Please see below for exclusions specific to this program.
|Priority||iOS, Android||Web, Desktop, API|
Out of scope
Any domain/property of Upwork not listed in the targets section is out of scope. This includes any/all subdomains not listed above.
- Please note that the mobile web app is available at: upwork.com/mobile
- Information on the public messaging API is available at: developer.upwork.com and also attached to the listing.
Upwork - iOS and Android Applications
API Documentation: https://developers.upwork.com/
Credentials for this can be freely and easily self-provisioned:
When testing please only test against jobs that you have created - do not test against jobs owned by persons other than yourself
- All CSRF vulnerabilities will likely be evaluated at P4 level
- Social Engineering
- Uploading of any vulnerability or client-related content to third-party utilities (e.g. Github, DropBox)
- Network-layer D/DoS
- If you suspect an application-layer D/DoS, contact Bugcrowd to review the vulnerability. Do not proof-of-concept application-layer D/DoS attacks without prior consent.
- All attack payload data must use professional language (ex: “test” rather than “this has been hacked.”)
- If able to gain access to a system, accounts, users, or user data, stop at the recognition of and report. Do not dive deeper to determine how much more is accessible.
Additionally, the following vulnerabilities are considered too low of an impact, and will be marked as Out of Scope if submitted:
- Account/e-mail enumeration using brute-force attacks
- Any low impact issues related to session management (i.e. concurrent sessions, session expiration, password reset/change logout, etc.)
- Bypassing content restrictions in uploading a file without proving the file was received
- Clickjacking/UI redressing
- Incomplete or missing SPF/DMARC/DKIM records
- Issues related to password/credential strength, length, lock outs, or lack of brute-force/rate limiting protections
- Lack of SSL or Mixed content
- Missing Cookie flags
- Reflected file download attacks (RFD)
- Self-exploitation (i.e. password reset links or cookie reuse)
- URL Redirection
- Use of a known-vulnerable library which leads to a low-impact vulnerability (i.e. jQuery outdated version leads to low impact XSS)
- Vulnerabilities affecting users of outdated browsers, plugins or platforms
- Vulnerabilities that require the user/victim to perform extremely unlikely actions (i.e. Self-XSS)
- android:debuggable=”true” in Android Manifest
- android:allowBackup set to true (by default)
- Information disclosure via Toast messages
- Information leakage in backgrounding snapshots
- Information leakage in keystroke caching
- Copy & Paste disabled for sensitive fields
- Pasteboard data cached
- The application asks for more permission than its needs
- Two-factor authentication bypass that requires physical access to a logged-in device
- Any issue in the mobile app that can only be exploited on a rooted or jailbroken device
- Any issue exploited in the mobile app because an operating system vulnerability
- Local access to user data when operating a rooted mobile device
This list will be updated if we see a particular vuln that is systemic and site wide. Please check this list often. This is for your benefit and to save you the trouble of searching the analytics