MaxPatrol VM
Company: Positive TechnologiesBug bounty program for MaxPatrol VM
Rewards are paid to individual entrepreneurs and self-employed persons
Program description
Bug bounty program for MaxPatrol VM
The MaxPatrol VM bug bounty program focuses on identifying and validating vulnerabilities that could impact vulnerability management workflows, corrupt or misrepresent IT asset data, lead to incorrect risk prioritization, or enable MaxPatrol VM to be abused as an initial access vector into a customer environment.
MaxPatrol VM is a next-generation vulnerability management system that supports the end-to-end vulnerability management lifecycle: asset discovery and inventory, vulnerability identification and prioritization, remediation governance, and overall security posture assessment. Security issues in the product can directly influence decision-making, introduce defensive blind spots, and reduce an organization's ability to respond effectively to real-world threats.
Limitations
When the program launches, access to the product's test environments will be limited.
Broader access will be provided later, once the supporting infrastructure and operational procedures are finalized.
Broader access will be provided later, once the supporting infrastructure and operational procedures are finalized.
General information
Types of vulnerabilities eligible for review. We accept vulnerability reports in the following categories (including, but not limited to):
1. Web interface and management API
- Authentication/authorization bypass in the management interface that results in unauthorized access to system features.
- Bypassing access control restrictions, including access to another tenant's or organization's data in a multi-tenant architecture.
- Cross-site scripting (XSS) that could be used to hijack an active session or perform actions as the victim user.
- SQL injection (SQLi) or command injection in inputs used to manage assets, define vulnerability-processing rules, or generate reports.
- Insecure direct object references (IDOR) in API, enabling access to another user's or organization's data, configuration, or scan results.
2. Asset and data management
- Path traversal in report handling or file upload functionality that could enable arbitrary file read, deletion, or modification on the server.
- Asset data manipulation that causes incorrect host criticality and remediation prioritization, creating blind spots in defense.
- Circumventing data integrity controls to hide certain assets or vulnerabilities from MaxPatrol VM.
3. Scanning and analysis
- Evasion of vulnerability detection logic that leads to false negatives (existing vulnerabilities are missed).
- Server-side request forgery (SSRF) in information-gathering or validation features that could be used to target internal infrastructure components or third-party services.
- Breaking or degrading the retrospective analysis feature (used to detect newly disclosed vulnerabilities without rescanning), potentially causing stale or inaccurate security posture data.
4. Authentication and authorization
- Access control flaws that allow a low-privileged user to escalate privileges to a system administrator.
- Weaknesses in how credentials for white-box scanning are stored or transmitted, potentially enabling credential theft and reuse.
5. Product components and internal interactions
- Using MaxPatrol VM as an intermediary node to attack its own components, internal services, external integrations (LDAP, SSO, and more), or other systems in the customer environment.
Note. Findings that do not present a practical security risk (for example, purely theoretical issues or reports without exploit validation) may be rejected or treated as informational and are not eligible for a bounty payout.
Rewards
Payout amounts are listed in the table below:
| Severity | Payout amount |
|---|---|
| Critical | RUB 300,000–500,000 |
| High | RUB 150,000–300,000 |
| Medium | RUB 50,000–150,000 |
| Low | RUB 0–50,000 |
Rewards are paid only for attack scenarios that can be reproduced on an officially supported product version that is fully patched with all available updates. Reports for end-of-support versions are accepted as well, but a payout for such issues is not guaranteed.
Vulnerability severity is assessed during triage and validation based on the issue's impact on the product security.
The product security team makes the final severity determination.
The product security team makes the final severity determination.
Participation requirements
Participants must be at least 18 years old.
Researchers aged 14–18 are allowed to participate only if they can present the written consent of a parent or a legal guardian.
Current Positive Technologies employees, as well as former employees whose employment ended less than three years ago, may take part in the program but are not eligible to receive a bounty payout.
Researchers aged 14–18 are allowed to participate only if they can present the written consent of a parent or a legal guardian.
Current Positive Technologies employees, as well as former employees whose employment ended less than three years ago, may take part in the program but are not eligible to receive a bounty payout.
Participant obligations:
- Follow the vulnerability disclosure rules of the Positive Technologies program and the Standoff 365 Bug Bounty platform.
- Follow the rules related to the handling of sensitive information. Do not gain access to data belonging to another user without the user's permission, change or destroy the data, or disclose any sensitive data obtained inadvertently during the vulnerability testing process or exploit demonstration. Deliberate access to sensitive data is prohibited and can be deemed illegal.
- Maintain communication with the security team, send them reports on discovered vulnerabilities according to the program requirements, and provide feedback if they have questions about the report.
- Do not publicly disclose any details of the vulnerabilities discovered. Positive Technologies retains the right to decide if and when information about the reported vulnerability will be published.
- Public disclosure of a vulnerability is allowed only after a fix is released and a publicly registered CVE/BDU identifier has been assigned.
- If a researcher requests disclosure of the report, Positive Technologies will initiate the coordination process to register a vulnerability identifier.
Rewards for reported vulnerabilities
No reward will be given for:
- Reports generated by security scanners and other automated tools.
- Disclosure of non-sensitive information (such as software name and version or technical characteristics and metrics of the system).
- Information about IP addresses, DNS records, and open ports.
- Reports of issues and vulnerabilities based on the product version without demonstrating exploitation.
- Reports of vulnerabilities whose exploitation is prevented by security tools, if the researcher does not demonstrate how to bypass the security tools.
- Reports of insecure SSL/TLS ciphers without demonstrating exploitation.
- Reports indicating the lack of SSL or other best current practices (BCPs).
- Reports of vulnerabilities already reported by other participants (duplicate reports).
- 0-day or 1-day vulnerabilities identified by our security team based on information from open sources.
- Reports of brute-force vulnerabilities without providing an attack method that is significantly more efficient than a straight-forward brute-force approach.