OKX: Program info

Broken link reports (Updated 31 Oct)

Broken links that cannot be taken over or do not pose a security risk may not be included, or the reward amount may be reduced. ($50)

New vulnerability tier (Updated on 27 Sep 2023)

Extreme: Up to $1,000,000

Vulnerabilities in essential assets that have the potential to result in significant business disturbances or unauthorized entry to OKX wallets, funds, or private keys of wallets.

IN-SCOPE WEB VULNERABILITIES

We are interested in the following vulnerabilities:

Extreme

• Vulnerabilities in critical assets capable of causing substantial business disruptions or enabling unauthorized access to OKX funds, OKX web3 wallets with funds or private wallet keys.

Critical

• Vulnerabilities that might jeopardise the security of funds or fees belonging to users or validators, or substantially weaken the token economy or trading mechanisms.
• Remote code execution on any OKC Chain
• Manipulation of blockchain validator, or multiple machines on the intranet
• Gaining control of essential backend super administrator privileges, potentially resulting in significant consequences, like widespread exposure of critical business information
• Exploitation of staking rewards above 10 million and also cause financial loss

High

• Vulnerabilities that could disrupt Blockchain validator and its performances
• SQL injection to system (backend loophole reports would be downrated, while submission in pack uprated if appropriate)
• Unauthorized access to sensitive data, including but not limited to bypassing authentication to access the backend, weak backend password, and SSRF that obtains considerable sensitive information from the intranet
• Unauthorized operation with fund, bypassing payment logic (successfully exploited)
• Serious logical design and process loopholes, including but not limited to loopholes that allow random user login and mass modification of account password, as well as logical loopholes that compromise the company's key business, except for verification code blasting
• Other vulnerabilities that can cause large-scale impact on users, including but not limited to self-propagating stored XSS on important webpages, stored XSS that can obtain and successfully use administrator authentication information
• Substantial leakage of source codes
• Indications of any insider trading or money laundering

Medium

• Vulnerabilities that affect users through interactions, including stored XSS on normal webpages and CSRF in core businesses.
• Unauthorized operations, including but not limited to bypassing authentication to modify users’ information and modifying users’ configurations.
• Logical loopholes in verification code that may make blasting through sensitive operations possible, such as random account login and random password retrieval
• Leakage of locally-stored sensitive encryption data (with effective use)
• Vulnerabilities that hinder trading, deposits and withdrawals, such as failure to cancel or place orders, or incorrect account history
• Subdomain takeover

Low

• Vulnerabilities that could affect OKC related nodes on stability or availability.
• Local denial-of-service vulnerabilities, including but not limited to local denial-of-service vulnerabilities on the client (caused by parsing of file formats and network protocols), and issues related to Android component access exposure and general application access
• General information leakage, including but not limited to web path traversal, system path traversal, and directory browsing, etc.
• Reflected XSS (including DOM XSS / Flash XSS)
• Normal CSRF
• URL redirection vulnerabilities
• SSRF with no echo nor successful use
• Social media account takeover (Official OKX social media accounts)

OUT-OF-SCOPE WEB 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:

• Reports from automated tools or scans
• False positive SQL Injection
  • To avoid submitting a false positive, please ensure that you are able to provide a working PoC that demonstrates the ability to retrieve the current database / current user name
• Spam vulnerability, mail spoofing, mail bomb, etc.
• Self-XSS
• Use of known-vulnerable library or component
• Clickjacking on pages with no sensitive actions
• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
• 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 or brute-force issues on non-authentication endpoints
• Missing best practices in Content Security Policy.
• Missing HttpOnly or Secure flags on cookies
• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
• Vulnerabilities only affect 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).
• 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
• Issues that require unlikely user interaction
• Vulnerabilities that are already known (e.g. discovered by an internal team)
• Best practice reports are not eligible for bounties but are appreciated.
• Wordpress related vulnerability
• Reports that state that software is out of date/vulnerable without a proof of concept

OUT OF SCOPE – MOBILE VULNERABILITIES

• Attacks requiring physical access to a user's device
• Vulnerabilities that require root/jailbreak
• Vulnerabilities requiring extensive user interaction
• Exposure of non-sensitive data on the device
• Reports from static analysis of the binary without PoC that impacts business logic
• Lack of obfuscation/binary protection/root(jailbreak) detection
• Bypass certificate pinning on rooted devices
• Lack of Exploit mitigations i.e., PIE, ARC, or Stack Canaries
• Sensitive data in URLs/request bodies when protected by TLS
• Path disclosure in binary
• OAuth & app secret hard-coded/recoverable in IPA, APK
• Sensitive information retained as plaintext in the device’s memory
• Crashes due to malformed URL Schemes or Intents sent to exported Activity/Service/Broadcast Receiver
• Any kind of sensitive data stored in-app private directory
• Runtime hacking exploits using tools like but not limited to Frida/ Appmon (exploits only possible in a jailbroken environment)
• Shared links leaked through the system clipboard
• Any URIs leaked because a malicious app has permission to view URIs opened.
• Exposure of API keys with no security impact (Google Maps API keys etc.)

Notes about IDOR Vulnerabilities Researchers must be able to prove a feasible way to gain an ID as an attacker and we will not accept reports where IDs are being brute forced.

Known issues

Please note that the OKX Security Team also actively looks for vulnerabilities across all assets internally. For reported issues that are already known to us, we will close them as duplicates. We seek your kind cooperation to respect our final decision and to refrain from making multiple negotiations once the decision has been made.

• Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
• Don’t spam forms or account creation flows using automated scanners
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission

• As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
• No vulnerability disclosure, including partial, is allowed for the moment.
• Please do NOT publish/discuss bugs

We are happy to thank everyone who submits valid reports, which help us improve security. However, only those who meet the following eligibility requirements may receive a monetary reward:

• You must be the first vulnerability reporter.
• The vulnerability must be a qualifying vulnerability
• Any vulnerability found must be reported no later than 24 hours after discovery, and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, including attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of ours or one of its contractors.
• ONLY USE YOUR HackenProof ACCOUNT (in case of violation, no bounty will be awarded)
• Provide detailed but to-the-point reproduction steps

Reward List

• High-quality reports may be awarded an extra bonus. A high-quality report is a thoroughly written vulnerability report that includes (when applicable) a working proof-of-concept, root cause analysis, a suggested fix, and any other relevant information.

Known Issues

• Please note that the OKX Security Team also actively looks for vulnerabilities across all assets internally. For reported issues that are already known to us, we will close them as duplicates. We seek your kind cooperation to respect our final decision and to refrain from making multiple negotiations once the decision has been made.