Security Bounty Program

Overview

Data security and privacy are key aspects of our service as laid out in our Security Policy.

To participate you will need to follow a few rules:

• Be a good citizen. Do not disturb the service. Follow the terms and conditions.
• Only test with your data. Do not interact with other accounts.
• Create only few user accounts.
• If you gain access to our system, report it immediately.
• Do not publish any information regarding the vulnerability until we have fixed it.

Finally, please keep in mind this security bounty program doesn’t concern regular bugs in our application or APIs. We're only interested in security flaws allowing intruders to gain access to data of other users. If you wish to report a regular bug use the contact form.

Reports we're interested in

• Tampering with data of other users.
• Bypassing our API's security.
• Cross-site scripting (XSS).
• Server-side code execution.

In scope

• Website: www.opencagedata.com
• API: api.opencagedata.com
  Documentation, we allow non-https access, CORS
• Our blog: blog.opencagedata.com,
  Is a pre-generated static site and the issue would need to have significant impact
• Public repositories: github.com > opencagedata

Examples of Non-Qualifying exploits

• Denial of service attacks.
• Social engineering.

Reports we don't want

• SSL or DNS best practices (DNSSEC, CAA)
  We review those regularly
• Hardware or CPU related (e.g. BEAST, CRIME, BREACH, Lucky Thirteen)
  Unless shown how they can exploited through our website or API
• Email spoofing (SPF, DMARC, DKIM, MTA STS)
• Auto-expire password or force users to regular change passwords
  We believe users should use password managers and two-factor authentication these days
• Choosing weak password during registration
  We display a password strength estimation (weak, medium, strong) below the password field. Estimating is hard so we allow users to ignore our advise. Password must still be at least 8 characters long.
• Enabling autocomplete=off attribute on password fields
  Modern browsers ignore the attribute
• Issues concerning: status.opencagedata.com
  The site is hosted by a third party and outside of our control
• Found OpenCage geocoding API key on a public website
  We ask our users to secure their API keys, but exposure itself is not a security issue
• Mass submitting contact form
  There's limits by IP, address, timing, total number in place
• Passwords over 512 character length cause error
  The error is instant, thus no DOS effect
• Email addresses extracted from stealer logs. Those aren't an indication of leaks from our systems, but originate from malware on users' computers. We're happy to disable any affected accounts but lists we received so far didn't didn't match email addresses in our records. The lists seem to be low quality, very old (already dealt with years ago) or possibly fake.
• Reports related to the Geomob site.
  It is not part of our core business.

Rewards

Our reward system is flexible and doesn't have any strict upper or lower limit. The amount of the reward will depend on the severity of the vulnerability. The amount of the reward and whether or not a vulnerability qualifies will be at our sole discretion.

Rewards will be sent by bank transfer (Wise if the recipient is not in the Eurozone, we will not make financial rewards to countries not supported by Wise) once the vulnerability has been fixed and the reporter has supplied a valid invoice. All international transfer and conversion fees will be paid by the recipient.

We only award one bounty per vulnerability. If we receive multiple reports, the first one will receive the reward.

Report submission

Please submit to the email address in our security.txt file.

Hall of Fame

Thanks to the following researchers who have helped us debug various issues.

• 2025
• 2024
• 2023
• 2022
• 2021
• 2020
• 2019