Supported languages:
Bounty rules:
The Bug Bounty program only accepts and pays for reports on vulnerabilities previously unknown to the VK team.
The types of vulnerabilities eligible for bounties are listed in the "Maximum bounty" table at the end of the rules for the Bug Bounty program rules.
The bounty amounts shown in the description are for reference only.
The applicability and amount of a bounty may depend on the severity of the problem, novelty, likelihood of use, environment, and/or other factors.
The VK security team makes a bounty decision for each message individually.
Any vulnerabilities not listed in the "Bounty amount" table are paid for at the discretion of the program owner.
Scope of the Bug Bounty program:
Mobile apps:
Domains:
Tier 1:
ok.ru, m.ok.ru, api.ok.ru, connect.ok.ru, paymentnew.ok.ru, apptracer.ru, *.apptracer.ru, api-hprof.odkl.ru
Tier 2:
*.tamtam.chat, *.ok.ru, mycdn.me, *.mycdn.me, okcdn.ru, *.okcdn.ru, ok.me, apiok.ru
Out of scope domains:
insideok.ru, okl.lt
Important:
MitM, open redirects, SSL misconfigurations, etc. are not accepted unless additional vectors are defined (e.g., the ability to steal a session token via a remote vector for open redirects).
Vulnerabilities in the TamTam messenger are only accepted with a critical risk level.
Public 0-day/1-day vulnerabilities may be considered duplicates for several weeks after a vulnerability is published if our team knows about the vulnerability from open sources and we are working to eliminate or fix it.
Bug reports submitted by current or former employees (up to one year from the end of employment) of the VK Group are accepted without payment.
When testing RCE, SQLi, LFI, LFR, or SSTI, only the use of the MINIMUM possible POC (sleep, reading /etc/passwd, curl) is allowed. If you want to test the possibility of privilege elevation on a server, please create a report and write that you want to elevate privileges.
Publishing or disclosing bug report and/or any details associated with VK products without approval from VK's information security team is prohibited. We reserve the right to refuse any request for public disclosure of the report.
Vulnerability testing should only be done on your own accounts.
Limitations on the Bug Bounty program's scope:
It is recommended to limit all scanning tools to 10 requests per second.
We do not accept or review:
- Bug reports from vulnerability scanners and other automated tools;
- Disclosure of information that is not confidential, for example, the version of a product;
- Disclosure of information about a user that is public, for example, a user's nickname;
- Bug reports based on the version of a product/protocol (e.g. TLS version) without demonstrating the actual presence of a vulnerability;
- Bug reports about a missing security mechanism/current best practice (e.g. missing - CSRF token, framing/clickjacking protection) without demonstrating an actual impact on the security of users or the system;
- Messages about published and unpublished SPF and DMARC policies;
- Cross-site request forgery leading to logout (logout CSRF);
- Vulnerabilities in partner products or services, unless Mail.Ru or VK.com users/accounts are directly affected;
- Security of rooted, jailbroken, or otherwise modified devices and applications;
- Ability to reverse engineer an application, or the lack of binary protection;
- Open redirection vulnerabilities are accepted only if a security impact is identified, such as the possibility of stealing an authorization token;
- Injecting unformatted text, audio, images, or video into a server response outside of the user interface (for example, into JSON data or an error message), unless doing so replaces the user interface, changes the behavior of the user interface, or results in other negative consequences;
- Same site scripting, reflected downloads, and similar attacks with questionable impact;
- CSP-related bug reports;
- IDN homograph attacks;
- XSPA (scanning the IP addresses/ports of external networks);
- Excel CSV formula injection;
- Scripting in PDF documents;
- Attacks that require full access to a local account, browser profile or physical access to the device;
- Attacks based on scenarios where a vulnerability in a third-party site or application is required as a prerequisite and is not demonstrated;
- Theoretical attacks without proof of feasibility;
- Denial of service (DoS) vulnerabilities, for example - sending a large volume of requests or data (flooding);
- Ability to send a large number of messages;
- Ability to send spam or a malware file (for example, registration or password recovery spam);
- Disclosure of information through external links not controlled by Mail.Ru or VK.com (for example, Google dorking of private protected areas of robots.txt);
- Disclosure of unused or properly restricted JS API keys (for example, an API key for an external map service);
- Ability to perform an action not available through the user interface and without identified security risks;
- Vulnerabilities associated with the use of phishing and other social engineering techniques;
- Disclosure of /metrics, /status, htaccess or similar without a demonstrated information security threat (for example, disclosure of private API methods, tokens);
- Blind SSRF vulnerabilities without demonstrating a threat to the service's information security in the report;
- EXIF metadata in images;
- SSRF vulnerabilities that involve sending requests via rentgen*.smailru.net, snipster.*.go.mail.ru, mpr*.m.smailru.net, rs-proxy*.i.smailru.net or other proxies specifically designed to protect against SSRF;
- Vulnerabilities that disclose only user accounts but not passwords or other personal data.
We consider bug reports as informational if:
- The vulnerability discloses information about hacked accounts of external users for Mail.Ru or VK.com services;
Maximum bounty:
| Vulnerability | Tier 1 | Tier 2 |
|---|
| Remote Code Execution (RCE), server-side | 3 600 000 ₽ | 250 000 ₽ ‑ 1000 000 ₽ |
| Remote Code Execution (RCE), mobile app | 600 000 ₽ | 150 000 ₽ |
| SQL Injection (SQLi) | 2 400 000 ₽ | 240 000 ₽ |
| Local/Remote File Inclusion (LFI, RFI) | 2 400 000 ₽ | 240 000 ₽ |
| XML External Entity (XXE) | 2 400 000 ₽ | 240 000 ₽ |
| Server-Side Request Forgery (SSRF) (except dedicated isolated proxies) | 1 200 000 ₽ | 120 000 ₽ |
| Server-Side Request Forgery (SSRF) (except dedicated isolated proxies), blind | 240 000 ₽ | 30 000 ₽ |
| Insecure Direct Object Reference (IDOR) | 20 000 ‑ 1200 000 ₽ | 20 000 ‑ 120 000 ₽ |
| Admin panel / support portal auth bypass | 720 000 ₽ | 240 000 ₽ |
| Blind XSS in admin panel / support portal | 360 000 ₽ | 120 000 ₽ |
| Cross-Site Scripting (XSS) | 30 000 ‑ 120 000 ₽ | 30 000 ₽ |
SSRF's are paid for only when demonstrate demonstrating a threat to the service's information security in the report.
Self-XSS, XSS specific to non-common browsers (e.g. IE), blocked CSPs and other vectors without proven script execution are generally accepted without reward. Subdomain takeovers are considered under the same severity/conditions as cross-site request forgery (CSRF).
Detailed error output, local installation path, phpinfo() output, performance counters, etc. are not considered confidential; such messages are usually accepted without payment of a bounty. Messages about disclosure of software versions are not accepted.