PT Application Firewall
Company: Positive TechnologiesBug bounty program for PT Application Firewall
Rewards are paid to individual entrepreneurs and self-employed persons
Program description
Bug bounty program for PT Application Firewall
The PT Application Firewall bug bounty program focuses on identifying and validating vulnerabilities that may enable web protection bypass, weaken attack filtering, compromise the UI for security policy management, or allow the WAF to be abused as a bypass point or as an attack amplifier against protected applications.
PT Application Firewall is a web application firewall (WAF) that helps prevent vulnerability exploitation without modifying the protected application. It inspects inbound and outbound HTTP/HTTPS traffic, enforces security policies, and performs behavioral analysis. Vulnerabilities in a WAF can allow attackers to bypass protections or undermine detection logic, potentially giving defenders a false sense of 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/authorization bypass in the management UI that results in unauthorized access to security policy configuration.
- Cross-site scripting (XSS) in rule configuration or log viewing pages that could be used to hijack an administrator session or execute actions as the administrator.
- SQL injection (SQLi) in input fields used to create custom rules, filters, or exclusion lists.
2. Protection engine (WAF bypass)
- HTTP/HTTPS parser evasions using non-standard encodings, request splitting, or HTTP request smuggling.
- Filter evasion via Unicode normalization, case manipulation, non-standard HTTP methods, or crafted request formats.
- Circumventing geolocation/IP restrictions by spoofing client IP headers or leveraging CDNs, proxies, or multi-hop setups.
- Evading rate limiting through distributed traffic or by manipulating identifiers used for session tracking.
- Evading anti-bot defenses (CAPTCHA, JavaScript challenges) using automation and challenge bypass techniques.
3. Traffic processing and analysis
- Flaws in protocol parsers (HTTP, XML, JSON) that could cause memory leak, denial of service, or remote code execution (RCE).
- Evasion of file upload inspection using polymorphic payloads or uncommon data formats.
- Breaking or degrading SSL/TLS decryption/inspection by leveraging unusual cipher suites, non-standard handshake parameters or protocol versions, leading to incomplete or incorrect analysis of encrypted traffic.
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.