Introduction & Brand Promise

ABB is a leading global technology company that energizes the transformation of society and industry to achieve a more productive, sustainable future. By connecting software to its electrification, robotics, automation and motion portfolio, ABB pushes the boundaries of technology to drive performance to new levels. With a history of excellence stretching back more than 130 years, ABB’s success is driven by about 105,000 talented employees in over 100 countries.

ABB looks forward to working with the security community to find vulnerabilities in order to keep our business, community and customers safe. If you have information related to security vulnerabilities of ABB products or services, we want to hear from you.

Terms & Conditions

By participating as a Finder in any Program which ABB Information Systems Ltd. (ABB) posts to the HackerOne Platform, you (You or the Finder) agree to the following terms and conditions: F1828095

Response Targets

ABB Information Systems Ltd will make a best effort to meet the following SLAs for hackers participating in our program:

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

• ABB are not currently accepting or approving disclosure requests and we do not allow you to disclose any vulnerabilities (even resolved ones) detected during your participation in the Program to any person other than HackerOne for the purpose of establishing Customer Reports in compliance with the HackerOne Platform’s processes without ABB’s prior written consent.
• Follow HackerOne's disclosure guidelines.

Program Rules

• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
  • Provide a detailed summary of any vulnerability, including the Target, steps, tools, and artifacts used during discovery. If possible, share the logs generated by the security tools.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
• When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
• Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
• Social engineering (e.g. phishing, vishing, smishing) of ABB’s employees, customers, or vendors is prohibited.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
• Do perform testing using only accounts that are your own personal/test accounts or an account that you have explicit permission from the account holder to utilize.
• Exercise caution when testing to avoid negative impact to customers and the services they depend on.
• Stop testing if you are unsure about the impact it may have on our ABB’s systems. If you think you may cause, or have caused, damage with testing a vulnerability, report your initial finding(s) and request authorization to continue testing.
• Do not cause harm to ABB, its employees, customers, or others.
• Do not compromise the privacy or safety of ABB, its customers, employees or any third party or the operation of ABB services or provision of ABB’s products. Specifically:
  • Contact ABB via [email protected] immediately if You inadvertently encounter Personal data.
  • Do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability to ABB.
  • Avoid privacy violations, destruction of data, and interruption or degradation of ABB products or services (including denial of service).
  • Delete any data obtained from any finding once the finding is submitted.
• Do not disrupt or compromise any data or products that is not your own.
• Do not Brute force credentials or guess credentials to gain access to systems.
• Do not participate in denial of service attacks.
• Do not upload shells or create a backdoor of any kind.
• Do not engage or target any ABB employee, customer, or vendor during your testing.
• Do not attempt to extract, download, or otherwise exfiltrate data that you believe may have PII or other sensitive data other than your own.
• Do not change passwords of any account that is not yours or that you do not have explicit permission to change. If ever prompted to change a password of an account you did not register yourself or an account that was not provided to you, stop and report the finding.
• Do not do anything that would be considered a privacy violation, cause destruction of data, or interrupt or degrade our ABB products or service.

Program Eligibility

• You agree and adhere to the Program Rules and Legal terms as stated in this policy.

• You are the first to submit a sufficiently reproducible report for a vulnerability in order to be eligible for the report to be accepted and Triaged.

• You are available to supply additional information, as needed by our team, to reproduce and triage the issue.

• Publicly-known Zero-day vulnerabilities will be considered for eligibility.

  • Zero‑day vulnerabilities affecting ABB assets are accepted for reporting, provided the researcher supplies clear, reproducible steps demonstrating the issue.
  • Researchers must not perform any denial‑of‑service (DoS) testing under any circumstances when verifying a zero‑day vulnerability.
  • Publicly known zero‑day vulnerabilities are eligible for submission, but remediation timelines may be delayed until the relevant vendor releases an official patch.
  • ABB will process and track the report. However, full resolution actions will begin only once an upstream fix is available.

• Out-of-scope vulnerability reports or reports that are technically reproducible but pose a very low security impact are likely to be closed as Informative.

• ABB employees and third-party assets contractors/employees are not eligible for participation in this Program.

Scope

Please see our list of assets below in the structured scope, and feel free to report findings for any other domain not listed here for which you are confident that it belongs to ABB.

• Submit Even If the Domain Appears Out of Scope If any domain (even one not listed in ABB’s official scope) leaks ABB confidential, sensitive, or internal information, researchers are encouraged to submit the report. ABB will handle triage and determine final validity.
• ABB Will Conduct a Preliminary Validation For reports originating from domains not explicitly listed in the scope, the ABB security team will perform an initial assessment to determine whether:
  • The data belongs to ABB,
  • The asset is indirectly ABB‑controlled,
  • The vulnerability has security impact relevant to ABB.
  • ABB will then classify the report as accepted, informational, or out-of-scope based on the findings.

#Information Leakage Policy Addendum (VDP) #Accepted: Credentials/PII/Sensitive Data Leakage

• ABB accepts reports demonstrating exposure of credentials, PII, or sensitive data on ABB‑controlled assets, including but not limited to:
• passwords, API keys, access tokens, client secrets, SSH keys, cloud credentials, database connection strings, PII such as names, email addresses, phone numbers, employee IDs, device IDs, account numbers, internal URLs, source code, CI/CD logs, environment variables, and confidential documents. This also includes sensitive data exposed via request/response headers, URLs, referers, error messages, or logs, and exposures that occur during redirection from an ABB domain to a third‑party service.

#In‑Scope Information Leakage Types

• Credentials exposure: Any publicly accessible or easily retrievable username/password, API keys, access tokens (OAuth/JWT), client secrets, SSH keys, cloud credentials, database connection strings, or embedded credentials (in code, config, mobile bundles, containers, CI/CD logs).
• PII exposure: Direct, indirect, or inferable PII (e.g., name, email, phone, address, employee IDs, device IDs, account numbers, HR data) accessible without authentication or with minimal/default authentication; data-in-transit leakage via headers, URLs, referers, error messages, logs.
• Sensitive business data: Internal URLs, private repository contents, system configuration, debug endpoints, source code, secrets in environment variables, or confidential documents accidentally exposed (e.g., via public cloud buckets, git history, CI artifacts).
• Third‑party redirections: Where ABB domains redirect to another app/service and leak credentials/PII during the redirect chain (headers, query strings). These fall in scope for ABB if initiated by an ABB asset; ABB may coordinate with the third party as needed.
• Critical: Any validated credential with privileged access (admin, service, production), or bulk/unauthenticated PII accessible publicly.

##Prohibited Methods Social engineering (phishing, vishing, smishing) remains prohibited. Do not use exposed credentials to access accounts/systems, and do not mass‑download PII or sensitive data

Security Incident & Vulnerability Prioritization Classification

Priority, Severity, and Response Assignment Model

Note - H1 triage team: Immediately route any findings involving compromised credentials, subdomain takeover, PII exposure, or other sensitive data leakage and the above-mentioned data leakage findings to ABB Information Systems Ltd Team, as these may constitute security incidents.

| Priority | Category | Risk Level | Risk Score | Description | |----------|------------------------|------------|-------------|--------------|-------------------| | Incident | Security Incident | Critical | 9.1 – 10 | Any report indicating compromised credentials, subdomain takeover, PII exposure, or sensitive data leakage. Immediately assigned to ABB Information Systems Ltd since this can be an incident. | | P1 | Security Vulnerability | High | 7.0 – 8.9 | High‑severity vulnerability on a non‑compromised asset. | | P2 | Security Vulnerability | Medium | 4.0 – 6.9 | Medium‑severity vulnerability on a non‑compromised asset. | | P3 | Security Vulnerability | Low | 0.1 – 3.9 | Low‑severity vulnerability on a non‑compromised asset. |

#Priority Focus Areas for Submissions

###We highly value vulnerability reports that address the following critical security issues:

• Exposure of sensitive data, including Personally Identifiable Information (PII)
• Subdomain takeover risks
• Account takeover
• Remote Code Execution (RCE) vulnerabilities
• Authentication bypass scenarios
• Cross-Site Scripting (XSS)
• Broken access control mechanisms
• SQL Injection or equivalent injection flaws
• Server-Side Request Forgery (SSRF)
• Malicious file upload vulnerabilities
• XML External Entity (XXE) attacks
• Leakage or exfiltration of AWS credentials
• Misconfigurations in cloud infrastructure leading to data exposure

Out of scope vulnerabilities

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• ABB Products related findings. (Please use instructions in this link: Cyber security alerts and notifications — ABB Group (global.abb) for finding related to ABB Products)
• Reports from automated tools or scans
• Issues without clearly identified security impact (such as clickjacking on a static website), missing security headers, or descriptive error messages
• Missing best practices, information disclosures, use of a known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)
• Forms missing CSRF tokens without evidence of the actual CSRF vulnerability
• Self-exploitation (e.g. cookie reuse)
• Reports of insecure SSL/TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)
• Password complexity requirements, account/email enumeration, or any report that discusses how you can learn whether a given username or email address has a ABB-related account
• Self Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user
• POST-based Reflected Cross-site Scripting (XSS) vulnerabilities (Unless supporting documentation can be provided, illustrating how the vulnerability can be leveraged to exploit another entity directly from an ABB trusted domain.)
• Social engineering of ABB employees or contractors
• Any physical attempt against ABB property or data centers
• Presence of autocomplete attribute on web forms
• Missing secure cookie flags on non-sensitive cookies
• Denial of Service service attacks or any activity that could lead to the disruption of our service
• Banner identification issues (e.g., identifying what web server version is used)
• Open ports which do not lead directly to a vulnerability
• Publicly accessible login panels
• Attacks requiring MITM or physical access to a user's device
• Previously known vulnerable libraries without a working Proof of Concept
• Comma Separated Values (CSV) injection without demonstrating a vulnerability
• Missing best practices in SSL/TLS configuration
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• Rate limiting or bruteforce issues on non-authentication endpoints
• Missing best practices in Content Security Policy
• Missing security-related HTTP headers which do not lead directly to a vulnerability
• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)
• Tabnabbing
• Open redirect - unless an additional security impact can be demonstrated
• Issues that require unlikely user interaction
• Speculative reports about theoretical damage without concrete evidence or some substantive information indicating exploitability
• Non-ABB hosted dealership websites

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep ABB Information Systems Ltd and our users safe!