By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Intigriti Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Introduction

At OVO, we're committed to keeping your energy services secure, and that means protecting your data and account information. We've got a dedicated team working hard to keep OVO safe, but we know there's always room for improvement.

That's where you come in! We value your help in identifying any potential vulnerabilities in our systems. By sharing your findings, you'll be playing a vital role in making OVO even safer for everyone.

We do our best to catch and fix any issues before they become a problem, but we believe that getting fresh perspectives is key to uncovering any hidden vulnerabilities. Together, we can build a more secure OVO. Good luck and happy hunting!

Our worst-case scenarios are:

• Anything that could lead to or aid an attacker to attack our customers, commit fraud, or impact the services we provide within the in-scope assets is our way case scenario.

Any useful infrastructure information:

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:

Program feedback link
Please note this form will be checked periodically and should not be used for submission or support queries.

Known Issues (date last updated: 24/06/2024)

No known issues currently, this is a new programme.

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

Domains

• Any domain that is not listed in the Domains section, is out of scope for this program

General

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• Use of personal OVO Energy accounts (with private or intigriti.me email addresses)
• 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

This program follows Intigriti's contextual CVSS standard.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please inquire with Intigriti

Credentials:
None provided.
Please do not target customer accounts you do not own.

Just a heads up: If you choose to use your own money or personal OVO account for testing, please be aware that we cannot guarantee reimbursement in the event of any loss.