By participating in this program, you agree:

• To follow the Intigriti Community Code of Conduct.
• To follow the Intigriti Researcher Terms & Conditions.
• To follow the requirements and limit your activities to the scope of the program described herein.
• To not discuss or disclose vulnerability information with anyone not authorized by Oura without prior written consent from Oura (including, but not limited to, PoCs on YouTube and Vimeo).
• That you meet the criteria for this program as described herein.
• That your Submission and report meet the criteria for this program as described herein.
• That you will not attempt to access any personal information or anyone else’s data, including without limitation by exploiting a vulnerability.
• That you are not currently, nor have you been an employee of Oura, or an Oura affiliate within 6 months prior to submitting a report.
• That you are not currently, nor have you been under contract to Oura or an Oura affiliate within 6 months prior to submitting a report.
• That you are neither a family nor household member of any individual who currently or within the past 6 months meets or met the criteria listed in the two bullet points directly above.

Third-Party Data and Personal Information

You are not authorized to access anyone else's data or personal information, including without limitation by exploiting a vulnerability. If during your research or testing you interact with or obtain access to third-party data or personal information, you must:

• Stop your testing immediately and cease any activity that involves the data or personal information or the vulnerability.
• Do not save, download, copy, store, transfer, share, disclose, or otherwise retain the data or personal information.
• Alert Oura immediately and fully support our investigation and mitigation efforts.

Validation times

We aim to respond to responsible disclosures within seven (7) working days after the Intigriti triage team has validated your submission.

You will receive status updates every four (4) weeks until resolution of the reported issue is confirmed.

Safe Harbour

If you follow the program terms, the Intigriti Community Code of Conduct, and the Intigriti Researcher Terms & Conditions, we will not initiate a lawsuit or law enforcement investigation against you in response to your report. Please understand that this waiver does not apply to your activities that involve the networks, systems, information, applications, devices, data, products, or services of another party (which is not Oura).

The Vulnerability Disclosure Program is intended for the responsible disclosure of security vulnerabilities affecting in‑scope assets. Reports should describe the security issue clearly and include sufficient information to allow validation, while avoiding unnecessary impact to systems or data.

Application

• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that can't be used to exploit other users
• Verbose messages/files/directory listings without disclosing any sensitive information
• CORS misconfiguration on non-sensitive endpoints
• Missing cookie flags
• Missing security headers
• Cross-site Request Forgery with no or low impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits or the non-existence of rate-limits.
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking without proven impact/unrealistic user interaction
• CSV Injection
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Tokens leaked to third parties
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection without being able to modify the HTML
• Username/email enumeration
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• Not stripping metadata of files
• Same-site scripting
• Subdomain takeover without taking over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Blind SSRF without proven business impact (pingbacks aren't sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact

General

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that only work on software that no longer receive security updates
• Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
• Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
• Reports that state that software is out of date/vulnerable without a proof-of-concept

Mobile

• Shared links leaked through the system clipboard
• Any URIs leaked because a malicious app has permission to view URIs opened
• The absence of certificate pinning
• Sensitive data in URLs/request bodies when protected by TLS
• Lack of obfuscation
• Path disclosure in the binary
• Lack of jailbreak & root detection
• Crashes due to malformed URL Schemes
• Lack of binary protection (anti-debugging) controls, mobile SSL pinning
• Snapshot/Pasteboard leakage
• Runtime hacking exploits (exploits only possible in a jailbroken environment)
• API key leakage used for insensitive activities/actions

Hardware

• Destructive actions or vulnerabilities that require disassembling the product
• Attacks requiring physical modification to the device internals, such as chip decapping, probing, or soldering
• Hardware-based fault injection or glitching attacks (e.g., voltage or clock glitching) requiring physical tools
• Side-channel attacks (e.g., power analysis, electromagnetic emissions, or advanced timing attacks) requiring physical proximity or specialized lab equipment
• Environmental attacks (e.g., subjecting the hardware to extreme temperatures, rapid temperature cycling, or moisture beyond intended operating specifications)
• Reverse engineering of physical hardware components without demonstrating a tangible, remotely exploitable software or firmware vulnerability
• Physical theft or loss of the device and subsequent local data extraction (assuming standard local encryption and PIN protections are operating as intended)

Firmware

• Informational level findings (e.g., identifying firmware versions, partition layouts, or debug strings without an active exploit path)
• Extracting or flashing firmware directly from the hardware via internal physical interfaces (e.g., JTAG, UART, SWD, SPI)
• The absence of standard exploit mitigations (e.g., Stack Canaries, ASLR, NX) without a working, executable proof-of-concept
• Known vulnerabilities in older firmware versions (downgrade attacks)
• Hardcoded keys, certificates, or credentials that are uniquely provisioned per device and cannot be leveraged for a fleet-wide attack or broader privilege escalation
• Any other findings that lack an exploit and reproducible proof of concept

This program follows Intigriti's triage standards based on the proof of concept.

Where can we get credentials for the app?

This is a responsible disclosure program without bounties. We do not provide credentials for testing and testing against other member accounts is not authorized.