ABB’s Building Management Systems Found Vulnerable: Over 1,000 Flaws

January 24, 2025

Security researcher Gjoko Krstic has revealed a staggering number of vulnerabilities in ABB’s building energy management and control products, unveiling a critical threat to facilities like hospitals, airports, and stadiums. Krstic’s meticulous work uncovered over 1,000 security flaws in the ABB Cylon Aspect system and 35 more in the ABB Cylon FLXeon product. These vulnerabilities range from unauthorized file access to SQL injection, each creating avenues for remote hackers to seize control of the targeted systems. This discovery has sent shockwaves through the cybersecurity community, shedding light on the vast and concerning gaps in ABB’s security measures.

The sheer number of vulnerabilities uncovered by Krstic includes severe issues such as XSS (Cross-Site Scripting), CSRF (Cross-Site Request Forgery), SSRF (Server-Side Request Forgery), IDOR (Insecure Direct Object References), security bypasses, and Denial of Service (DoS). Even more alarming, these flaws could give malicious attackers full remote control over the systems. Despite such grave threats, ABB’s initial response was disappointingly slow. Krstic expressed frustration with ABB’s silent patching procedures and the company’s failure to publicly acknowledge the severity and scope of the issues.

Security Flaws and Their Ramifications

The critical vulnerabilities identified pose significant risks, especially for highly sensitive environments like hospitals, stadiums, and airports. Each of these facilities relies on the dependable operation of building management systems to ensure safety, comfort, and efficiency. The presence of security flaws in these systems drastically elevates the possibility of catastrophic outcomes, from life-threatening disruptions in hospitals to security breaches in airports. The high-severity ratings of these vulnerabilities underscore the imminent threat they represent, pushing the urgency for immediate remediation.

Krstic pointed out that ABB’s sluggish response potentially compromised the safety and security of countless facilities for an extended period. With only a fraction of the vulnerabilities assigned CVE identifiers, Krstic criticized the vendor for underreporting the criticality of each issue. Specifically, Krstic had expected more comprehensive reporting, with each vulnerable file or attack vector receiving its own CVE to reflect the significant risks adequately. His examination covered numerous PHP and Java files, many of which contained multiple flaws, thus amplifying the threat landscape.

The Handling of Vulnerability Disclosures

Krstic’s dissatisfaction with ABB’s handling of the disclosure process led him to take an unconventional route. Instead of reporting the issues directly to the vendor, as is typically done, he chose to disclose his findings through CISA (Cybersecurity and Infrastructure Security Agency) and CERT/CC (Computer Emergency Response Team Coordination Center). This approach underscores the necessity for vendors to exhibit transparency and promptness in addressing vulnerability reports. ABB’s initial reluctance to engage with Krstic and the subsequent insufficient public acknowledgment led to significant frustration within the cybersecurity community.

In response to growing criticism, ABB emphasized its commitment to cybersecurity, asserting that it has a formal policy for vulnerability handling and encourages appropriate channels for reporting. The company has since released patches and advisories, earning acknowledgment from CISA. This move, though delayed, signals a step toward rectifying the identified issues. However, the entire episode brings to light the essential need for better vulnerability handling processes and public transparency to foster stronger cybersecurity defenses.

Importance of Legacy System Updates

Another critical aspect highlighted by this incident is the importance of updating and maintaining legacy systems. ABB’s flawed products trace back to Cylon Controls, a company acquired by ABB four years ago. The codebase of these systems was 19 years old, pointing to longstanding vulnerabilities that had gone unaddressed. This situation exemplified the inherent risks associated with obsolete software systems that are not routinely updated, leaving them susceptible to various forms of cyberattacks. Ensuring the security of such legacy systems is paramount, given their prevalent use in vital infrastructure.

Moving forward, it’s crucial for companies like ABB to prioritize cybersecurity practices diligently. The need for regular updates, patches, and a proactive approach to handle vulnerabilities cannot be overstated. Krstic’s findings serve as a stark reminder of the potential dangers when these practices are neglected. A collaborative approach between researchers and vendors is imperative to securing systems effectively. This case also underscores the significant role of researchers in identifying and reporting vulnerabilities to protect essential infrastructure from malicious threats.

Conclusion: The Road Ahead

Security researcher Gjoko Krstic has brought to light a whopping number of vulnerabilities in ABB’s building energy management and control products, posing a significant threat to facilities such as hospitals, airports, and stadiums. Krstic identified over 1,000 security flaws in the ABB Cylon Aspect system and an additional 35 in the ABB Cylon FLXeon product. These weaknesses include unauthorized file access and SQL injections, offering hackers remote access to take control of these systems. This discovery has sent shockwaves through the cybersecurity community, highlighting extensive and concerning gaps in ABB’s security protocols.

Krstic unveiled severe vulnerabilities, including Cross-Site Scripting (XSS), Cross-Site Request Forgery (CSRF), Server-Side Request Forgery (SSRF), Insecure Direct Object References (IDOR), security bypasses, and Denial of Service (DoS). Alarmingly, these issues could enable attackers to gain full remote control over the systems. Despite these serious risks, ABB’s initial response was notably slow. Krstic voiced frustration over ABB’s silent patching approach and the company’s reluctance to publicly acknowledge the critical severity of the problems uncovered.

Subscribe to our weekly news digest.

Join now and become a part of our fast-growing community.

Invalid Email Address
Thanks for Subscribing!
We'll be sending you our best soon!
Something went wrong, please try again later