Other is a special program for reports on critical VK security vulnerabilities not covered by other Bug Bounty programs.
We accept vulnerability reports only if the vulnerability was previously unknown to the VK team.
The types of vulnerabilities eligible for bounties are listed in the "Rewards" section 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 "Rewards" section are paid for at the discretion of the program owner.
This program covers services and products related to or managed by VK but hosted outside the VK infrastructure: fresh and non-integrated acquisitions, domains not mentioned in other programs, various cloud services and hosted off-infrastructure solutions, it also covers non-production hosts (e.g. staging and demo installations) of VK projects in VK CS cloud hosting.
Bugs identified at YCLIENTS and YPLACES are accepted as informational and are not paid for.
*.my.games and all services related to My.GAMES or MGVC and their partners.
*.vkcs.cloud, *.algoritmika.org, *.yaklass.ru, *.umschool.net, *.code-class.ru, *.summerstage.ru, *.vk-stadium.ru, *.bargipsy.com
Client-side vulnerabilities (XSS, CSRF) and bugs related to business logic, including privilege escalation within the product, are accepted without reward.
MitM and local attacks, open redirects, insufficient session validation, handling cookies after logout, 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).
Bugs identified on demo stands, dev infrastructure, domains used for training, delegated, externally hosted domains and partner services are accepted as informational and are not paid for.
0-day/1-day vulnerabilities may be considered as a duplicate within several weeks after vulnerability details publication.
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, SSTI it is allowed to use only MINIMALLY possible POC for proof (sleep, accessing /etc/passwd, curl).
Publishing or disclosing bug report details without approval from VK's information security team is prohibited. We reserve the right to refuse any request for public disclosure of the report.
It is recommended to limit all scanning tools to 10 requests per second.
Vulnerability | Maximum bounty |
---|---|
Remote code execution (RCE) | 120 000 ₽ |
Server-side Injections (SQLi or an alternative) | 60 000 ₽ |
Access to and work with local files (LFR, RFI, XXE) without jail / chroot / file type restrictions | 60 000 ₽ |
RCE/LFI in the dev infrastructure / isolated or virtualized process | 30 000 ₽ |
Non-blind SSRF (with the ability to read the response text), except for dedicated proxies | 30 000 ₽ |
Blind SSRF, except for dedicated proxies | 18 000 ₽ |
Server-side vulnerability involving disclosure (e.g. memory leaks / IDORs) of critical or highly sensitive application data | 0 ₽ - 60 000 ₽ |
Server-side vulnerability involving disclosure (e.g. memory leaks / IDORs) of protected personal data or sensitive client information | 0 ₽ - 60 000 ₽ |
Server-side vulnerability involving disclosure (e.g. memory leaks / IDORs) of sensitive application or infrastructure data / organizational role privilege escalation | 0 ₽ - 60 000 ₽ |
Admin/support authentication bypass | 30 000 ₽ |
Blind XSS in the admin/support interface | 18 000 ₽ |
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.