Coordinated Vulnerability Disclosure

At Inverid, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.

If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients, our systems and users of our systems.

Please do the following:

• Please adhere to the scope,

• E-mail your findings to cvd@inverid.com. Encrypt your findings using our PGP key to prevent this critical information from falling into the wrong hands,

• Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data, 

• Do not reveal the problem to others until it has been resolved, 

• Do not use attacks on physical security or social engineering, denial of service attacks, spam or applications of third parties, and 

• Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation. 

What we promise:

• We will respond to your report within 12 business days with our evaluation of the report and an expected resolution date.

• If you have followed the instructions above, we will not take any legal action against you in regard to the report.

• We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission.

• We will keep you informed of the progress towards resolving the problem.

• Unless you desire otherwise, we will add your name to our hall of fame for a maximum of 3 years and we will give your name as the discoverer of the problem in the public information concerning the problem reported.

• As a token of our gratitude for your assistance, we offer a reward for every valid report of a security problem that was not yet known to us. The amount of the reward will be determined based on the severity of the leak and the quality of the report. The minimum reward will be a €100 gift certificate. If we decide to reward you with a higher amount, then we will need an invoice from you.

• We strive to resolve all problems as quickly as possible, and we would like to play an active role in the ultimate publication on the problem after it is resolved.

^Scope

In scope for searching and verifying vulnerabilities in our systems: https://cvd.readid.com/

The following are out of scope:

Domains

Any other domain than cvd.readid.com is out of scope for this program.

General

• 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 receives 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.

• IDOR vulnerabilities are in scope, but if UUIDs have to be guessed (i.e. there is no structural method to obtain them), then the Attack Complexity will be considered High. Also, if the vulnerability can only be exploited from a session using login credentials, then Privileges Required will be considered “High”.

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate.

• Personnel and former personnel of Inverid and its related companies (including external consultants, partners and customers) are not eligible for a reward.

• ReadID servers necessarily allow unauthenticated access to API endpoints to be able to validate identity documents. Therefore, any finding about missing authentication measures or input validation in this context will be treated as invalid.

Application

• Self-XSS that cannot 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

• 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/account 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 are not sufficient)

• Disclosed/misconfigured Google Maps API keys

• Host header injection without proven business impact

Mobile

Copied data leaked through the system clipboard

• 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

• Snapshot/Pasteboard leakage

• Runtime hacking exploits (exploits only possible in a jailbroken environment)

• API key leakage used for insensitive activities/actions

Our PGP key

-----BEGIN PGP PUBLIC KEY BLOCK-----mDMEZe8DWBYJKwYBBAHaRw8BAQdA+VHd421I9dgrnwQaA1muidHc1LwEsSzanPis
F3JoHzq0PkludmVyaWQgQ29vcmRpbmF0ZWQgVnVsbmVyYWJpbGl0eSBEaXNjbG9z
dXJlIDxjdmRAaW52ZXJpZC5jb20+iJkEExYKAEEWIQQIPO27evPH5JPWxYS9bg2y
oqCuvgUCZe8DWAIbAwUJBaOagAULCQgHAgIiAgYVCgkICwIEFgIDAQIeBwIXgAAK
CRC9bg2yoqCuvlU2AQDdV2GI9rZv5GeqA2qy6QmxpllNk0zKWb7dNEWIEh8NeAD/
Tmmcrtq0KHTUQdLm8LO1M7hBshGjtQs0QV+fzun63gC4OARl7wNYEgorBgEEAZdV
AQUBAQdA1VajGal4QT3YkeOBFtTXqm6yeRzdVlteOOimW+FlH0MDAQgHiH4EGBYK
ACYWIQQIPO27evPH5JPWxYS9bg2yoqCuvgUCZe8DWAIbDAUJBaOagAAKCRC9bg2y
oqCuvvhOAP9b78PNfVeVcGxnsKX1Ws/WC23V+jJl7wT4JfCHjD5AfAD9GHgPl/s3
p8LErTg+tj1G1eWu/XdJK2P2beuZAIcRJAk=
=YYyT
-----END PGP PUBLIC KEY BLOCK-----

The terms and scope of our coordinated vulnerability disclosure policy are subject to change. The text in this document is adapted from a text written by Floor Terra and is published with a Creative Commons Attribution 3.0 Unported license.