EN

ATI.SU

Company: ATI.SU
ATI.SU is a freight exchange and the largest ecosystem of transport logistics services in Russia and the CIS. We are open to collaborating with external researchers to improve the security of our products.
Rewards are paid to individual entrepreneurs and self-employed persons
Program description

Rules for us

  • We respect the time and effort of researchers;
  • We respond within 5 business days;
  • We process reports within 10 business days after initial response;
  • We may extend processing times, but you will be informed about any delays;
  • We determine the reward amount within 10 business days after processing;
  • We do our best to keep you updated on our progress throughout the review.

Rules for creating entities to avoid disturbance for site users

Platforms: Create only private ones. Users won't see them without invitation.
Cargo: Create only on existing private platforms.
Vehicles: Create vehicles for unpopular routes (e.g., Lisbon to Hanoi) with extremely high rates (from 1000 RUB per kilometer).
Truckmarket Listings: Include "test" in the listing title. Archive the listing immediately after finishing your tests.
Tenders: Add only to private platforms.
Claims/Recommendations, Cargo/Vehicle Reviews, Orders, Documents: Do not send to real users.

Scope

Below are resources that are our primary focus for vulnerability research. For vulnerabilities discovered on these resources, we guarantee rewards according to this program's rules:
  • ati.su
  • job.ati.su
  • trace.ati.su
  • userdata.ati.su
  • billing.ati.su
  • api.ati.su
  • help.ati.su
  • tm.ati.su
  • id.ati.su
  • d.ati.su
  • tenders.ati.su
  • trucks.ati.su
  • r1.ati.su
  • files.ati.su
  • loads.ati.su
  • faq.ati.su
  • about.ati.su
  • news.ati.su
  • adv.ati.su
  • chat.ati.su
  • academy.ati.su
  • zen.ati.su
  • iOS - "ATI Cargo and Transport" version 221 (2.17.0) and later
  • Android - "ATI Cargo and Transport" version 221 (2.17.0) and later
While vulnerabilities can also be found on other resources matching *.ati.su domain, we want to emphasize that we cannot guarantee payments for such findings. Reports on additional resources will be reviewed individually based on asset criticality and significance.

What Vulnerabilities to Look For?

We're primarily interested in critical server-side vulnerabilities. However, we welcome submissions of other types of vulnerabilities. If you're unsure whether to report your finding or not, check if it's listed under "What Not to Submit?" section. If it's not there, you can report your detailed finding.
Below are examples of vulnerabilities that will be accepted for review and analysis, and are eligible for rewards (this list is not exhaustive):
  • Remote Code Execution (RCE)
  • Injections (SQL, XML, LDAP, etc.)
  • LFR/LFI/RFI
  • Server-Side Request Forgery (SSRF)
  • Insecure authentication/authorization, session management
  • Authorization bypass and account takeover
  • Business logic vulnerabilities (including fraud schemes related to system flaws)
  • Sensitive information leakage to third-party services
  • IDOR, privilege escalation, and other access control vulnerabilities
  • Disclosure of sensitive information or personal data

What Not to Submit?

  • Ability to perform actions that are unavailable through the UI without identified security risks
  • Disclosure of non-sensitive information such as product version, server file path, stack trace, etc.
  • Issues unrelated to security (for non-security issues, contact via technical support email at bb@ati.su)
  • Reports about potential DDoS attacks
  • Information about IP addresses, DNS records, and open ports
  • Disclosure of private IP addresses or domains pointing to private IP addresses
  • Vulnerability scanner reports and other automated tool outputs
  • Reports about publicly accessible login panels
  • Clickjacking
  • Root and jailbreak detection bypass
  • Reports about mobile application reverse engineering possibility
  • Leakage of confidential tokens (e.g., password reset token) to trusted third parties over secure connections (HTTPS)
  • Previously known vulnerable libraries without working proof of concept
  • Attacks requiring MITM on another's connection or physical proximity to another's device (e.g., NFC, Bluetooth, Wi-Fi attacks, and shoulder surfing)
  • Unlikely or theoretical attacks without proof of concept
  • Reports without detailed impact description

What Is Not Eligible for Rewards and will be closed as "Informative"?

  • Vulnerabilities requiring browser versions released 6+ months prior to report submission (or no longer supported)
  • Self-XSS
  • XSS in unpopular browsers (e.g., IE, browser versions older than 6 months)
  • Flash-based XSS
  • XSS without impact on sensitive data
  • CORS misconfiguration*
  • Use of outdated or potentially vulnerable third-party software*
  • Fraud or theft-related attacks
  • DoS-type attacks*
  • Insecurely configured TLS or SSL*
  • Disclosure of username, email, or phone number existence in the system
  • Full Path Disclosure
  • Disclosure of technical or non-sensitive information* (e.g., product version, software used, stack traces)
  • Missing security mechanisms or best practices without demonstrating real impact on user or system security* (e.g., security HTTP headers, cookie security flags, or CSRF protection)
  • Open Redirect without additional attack vector (e.g., authorization token theft)
  • Content spoofing on pages
  • Tabnabbing
  • Vulnerabilities requiring complex or unlikely user interaction scenarios
  • Vulnerabilities requiring malware, root access, or jailbreak on the device for exploitation
  • Missing best practices in DNS and mail service configuration (DKIM/DMARC/SPF/TXT)
  • Ability to send emails without content control and without restrictions
  • 0-day or 1-day vulnerabilities with official patches released less than two weeks agoтАФreward payment is at the discretion of ATI.SU security specialists and reviewed individually
  • Broken links to social media pages or unclaimed social media links and similar pages
  • Ability to create user accounts without restrictions
  • User enumeration
  • Disclosure of public user information
  • Missing notifications for important user actions
  • PDF document scripting
* тАФ without detailed attack vector description and proof of potential damage or harm.

What Is TEMPORARILY Not Eligible for Rewards and will be closed as "Informative"?

What Is TEMPORARILY Not Eligible for Rewards in Android and iOS Applications and will be closed as "Informative"?

  • Application can run on jailbroken or rooted devices - That is intentional.
  • Possibility of SSL pinning
  • Migration of third-party service keys to more secure storage
  • Possible app crashes/ANR
  • The cleartextTrafficPermitted flag in the manifest and HTTP usage in WebView
  • Any vulnerabilities related to authorization tokens

Participation Rules

  • By participating in our Bug Bounty program, you confirm that you have read and agreed to the "Participation Rules." Violation of the rules may result permanent ban or ;
  • Reports submitted by current or former employees (up to one year after termination) of ATI.SU are accepted without reward eligibility;
  • Any activity that could harm company applications, infrastructure, clients, or partners such as denial-of-service attacks and physical interference with infrastructure are prohibited;
  • Social engineering attacks such as phishing, vishing, smishing are prohibited;
  • It is permitted to Interact only with accounts you own or accounts that you have explicit permission from the account owner. If additional accounts are required, such as privilege escalation or Atis** crediting, contact us for assistance;
  • If confidential information is accessed during exploitation, it cannot be stored, transmitted, or processed in any other way after initial discovery. All copies of confidential information must not be retained and must be returned to ati.su;
  • Always limit exploitation to the minimum proof of concept necessary to demonstrate the vulnerability;***
  • Do not attempt to access ati.su accounts, data, or other users' accounts after exploiting other vulnerabilities. Report your findings, and request permission for additional testing;
  • Use the minimum impact for Proof of Concept to confirm a vulnerability. If it may affect other users or system availability, contact us for permission;
  • Follow the command execution demonstration rules specified below in this program;
  • Submit reports in Russian language only.
** тАФ Atis is the site's internal currency.
*** тАФ In some cases, the security team may request additional evidence proving the vulnerability.

Traffic Identification

Traffic generated by external security researchers may be classified as malicious. To prevent related issues, please add the following HTTP header to all outgoing requests: X-Bug-Bounty: Username.

RCE Testing Policy

Testing vulnerabilities that may lead to remote code execution must follow these rules:
During testing, all server actions are prohibited except:
  • Executing commands: ifconfig (ipconfig), hostname, whoami, id
  • Reading contents of /etc/passwd and /proc/sys/kernel/hostname (drive:/boot.ini, drive:/install.ini)
  • Creating an empty file in the current user's directory
    Any other actions require prior approval from our security specialists.

SQL Injection Testing Policy

Testing vulnerabilities that may lead to SQL command injection must follow these rules:
During testing, all server actions are prohibited except:
  • Retrieving current database information (SELECT database()), its version (SELECT @@version), current user (SELECT user(), SELECT system_user()), or hostname (SELECT @@hostname)
  • Retrieving database schema (SELECT table_schema), table list (SELECT table_name), and column names (SELECT column_name)
  • Executing mathematical, conversion, or logical queries (including SLEEP) without extracting data (except those listed above)
    Any other actions require prior approval from our security specialists.

File Upload and Read Policy

Testing vulnerabilities that may lead to arbitrary file reading on the server or arbitrary file upload must follow these rules:
Prohibited actions for file uploads:
  • Modifying, deleting, or replacing any files on the server (including system files), except those associated with your account or an account whose owner has explicitly consented
  • Uploading files that may cause denial of service (e.g., large files)
  • Uploading malicious files (e.g., malware or spyware)
    When gaining arbitrary file read access, all actions are prohibited except reading files such as /etc/passwd and /proc/sys/kernel/hostname (drive:/boot.ini, drive:/install.ini). Any other actions require prior approval from our security specialists.

Vulnerability Rewards

We pay rewards to external security researchers only for discovering previously unknown issues while following all "Participation Rules."
All vulnerability reports are reviewed individually based on the criticality of the system where the vulnerability was found and the vulnerability's own criticality.
VulnerabilityReward
Critical120,000тАУ250,000 тВ╜
High20,000тАУ120,000 тВ╜
Medium5,000тАУ20,000 тВ╜
Low0тАУ5,000 тВ╜

Vulnerability Severity Determination

We reserve the right to make the final decision regarding the seriousness of a discovered vulnerability. After receiving a report, we conduct an internal investigation and determine the severity level considering multiple factors, including:
  • Privilege level required to execute the attack
  • Difficulty of discovery and exploitation
  • User interaction requirement
  • Impact on integrity, availability, and confidentiality of affected data
  • Business and reputational risk impact
  • Number of affected users
  • Please note that our site uses two account types: verified and unverified (detailed information here). Under this program, vulnerabilities related to unverified accounts are assessed at a reduced coefficient since some security measures don't apply to them.
Notes
  • Contact email: BB@ati.su
  • Rewards are paid only if our security specialists verify that all conditions are met and the identified vulnerability is significant.
  • The paid reward amount is final and not subject to negotiation.

FAQ

How to Write a Good Report?

A report should describe one vulnerability or a chain of related vulnerabilities and must include:
  • Vulnerability description
  • Reproduction steps
  • Severity analysis
  • Clear impact description
  • Remediation recommendations
  • Vulnerable application URL
  • Type of vulnerability discovered
  • Screenshots or video confirming the vulnerability and demonstrating reproduction steps
  • Formatted request example from BurpSuite (or any other POC)
  • Code snippets in some cases
Failure to meet minimum requirements may result in reduced rewards. If a report lacks sufficient information to verify the vulnerability, no reward will be paid.
All information about the discovered vulnerability (including attachments) must be stored only in the report you submit and not posted it on any other external resources.

How Are Duplicates Handled?

We pay rewards only for the first received report, that was provided with all necessary information to reproduce the vulnerability. Any subsequent reports covering the same vulnerability will be marked as duplicates. Reports with similar attack vectors may also be considered duplicates if the security team determines that mitigation of one security finding from one report is sufficient to fix all registered attack vectors or bugs. A report may duplicate another researcher's report or an internal security team report.
Launched January 30, 2024
Edited March 26, 13:50
Program format
Vulnerabilities
Reward for vulnerabilities
by severity level
Critical
₽120K–250K
High
₽20K–120K
Medium
₽5K–20K
Low
₽0–5K
None
₽0–0
Excl. tax
Top hackers
Overall ranking
The ranking is still empty
Program statistics
₽2,485,540
Paid in total
₽24,368
Average payment
₽57,100
Paid in the last 90 days
280
Valid reports
293
Submitted reports
Description
Vulnerabilities
Ranking
Versions