PT Application Inspector
Company: Positive TechnologiesBug bounty program for PT Application Inspector
Rewards are paid to individual entrepreneurs and self-employed persons
Program description
Bug bounty program for PT Application Inspector
The PT Application Inspector bug bounty program focuses on identifying and validating vulnerabilities that may undermine AppSec analysis processes, falsify or skew SAST/DAST/IAST/SCA results, expose source code or analysis artifacts, or enable the platform to be abused as an initial access vector into customer environments.
PT Application Inspector is an end-to-end application security testing platform that brings together SAST, DAST, IAST, and SCA, along with signature- and pattern-based detection. It is used for applications ranging from public-facing services to high-impact enterprise and government systems. Security flaws in the platform can directly reduce the trustworthiness of findings and weaken SDLC security.
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 bypass in the management interface enabling unauthorized access to projects, analysis results, or system settings.
- Cross-site scripting (XSS) in inputs related to projects, scan settings, or reports that could lead to script execution in the victim's browser.
- Insecure deserialization in API endpoints that may result in arbitrary code execution and component compromise.
- Path traversal in source code upload/ingestion workflows that could allow arbitrary file read or overwrite on the server.
2. Source code analysis
- Manipulating analysis outcomes via injections into project metadata, causing false negatives/false positives in vulnerability findings.
- Incorrect processing of known vulnerabilities (CVEs) that could hide real issues in the target codebase or produce fraudulent findings.
3. Vulnerability database
- SQL injection in vulnerability search and filtering mechanisms that could expose system data or impact the system's availability.
- Cross-site scripting (XSS) in generated reports that could enable session hijacking or actions impersonating the victim user.
- Circumventing signature database integrity checks to tamper with or disable detection rules.
4. Rule engine
- Remote code execution (RCE) through custom analysis rules that are used to extend or customize analysis behavior.
- Unauthorized modification of built-in analysis rules due to vulnerable access control, leading to manipulated or unreliable scan results.
5. CI/CD integrations
- SSRF in integrations with CI/CD platforms (such as Jenkins, GitLab) that could be used to attack internal services or infrastructure.
- Exposure of CI/CD/build credentials used for automated pipeline scans.
- Remote code execution (RCE) through CI/CD hook handling, potentially compromising the build agents or development environment.
6. Architecture and deployment
- Container isolation weaknesses that could enable container escape and host compromise.
- Disclosure of sensitive information via error messages that could aid further exploitation or expose internal architecture details.
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.