Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


03:05 PM
Connect Directly

Siemens To Patch Major SCADA Authentication Holes Next Month

Researcher discloses serious security flaws in Siemens products

In the wake of a researcher's public disclosure of flaws in Siemens products that could let an attacker take over a control system without even knowing the username and password, Siemens today said it will issue security updates in January to fix product vulnerabilities.

Security researcher Billy Rios on Tuesday posted details in his blog of some of the vulnerabilities he and fellow researcher Terry McCorkle had found and reported to the ICS-CERT and Siemens in May. Siemens confirmed it was in the process of fixing the flaws today after Rios cried foul when the company appeared to deny the existence of the vulnerabilities that he and fellow researcher Terry McCorke had been working with the company on fixing.

Rios, who says he and McCorkle have reported some 1,000 bugs in industrial control system products during the past few years, decided to go public after a Siemens PR representative told a Reuters reporter following up on Rios' work that the company had no outstanding bug reports. "I had to go public," Rios says. "I just had the PR face of a major company telling a major media outlet that I'm a BS artist."

Rios says he reported to ICS-CERT in May an authentication bypass vulnerability in Siemens Simatic systems, which manage industrial control systems, as well as several other security issues. He went public this week with the authentication bypass bug as well as two other issues: that Simatic's default password is "100," and that if a user tries to change that password using a special character (question mark, hash mark, etc.), the password automatically reverts back to "100" without the user's knowledge.

That default password was likely used by the hacker "prof," who accessed the water utility system in South Houston, Rios says. "We had reported that bug in May, and we sat on our hands and waited" for Siemens to fix it, Rios says.

Meanwhile, a Siemens spokesperson says it was all a misunderstanding: The firm had no intention of denying vulnerabilities it was working on.

Siemens today issued this statement on its website: "Siemens was notified by IT experts (Billy Rios and Terry McCorke) about vulnerabilities in some of its automation products. These are the WinCC flexible RT versions from 2004 to 2008 SP2 and WinCC Runtime Advanced V11 and multiple Simatic panels (TP, OP, MP, Comfort). We are aware of the reported vulnerabilities, first reported in May 2011. Our development had immediately taken action and addressed these issues. The vulnerabilities will be fixed by security updates, first is planned to be issued in January 2012. In December 2011 further vulnerabilities have been reported which are currently under investigation. We thank Billy Rios and Terry McCorke for reporting the vulnerabilities."

But Rios says he's still not convinced there wasn't some sort of attempt by the SCADA firm to brush under the rug its latest vulnerability woes when Siemens was contacted by the Reuters reporter. "I would have had no problem if they had said, 'We have no comment,'" Rios says. "The spirit of [the response] was deceiving."

[Researchers have been finding gaping security holes in Siemens' process control products during the past few months. See Siemens Shows Up For Black Hat Demo Of SCADA Hack.]

The most serious of the three security issues Rios revealed publicly is the authentication bypass flaw, which he shows in detail here. "Even if you set a really strong password that's not guessable, I'm able to guess access to your system anyway," he says.

When the administrator logs into the Web HMI, the application returns a session cookie that can be easily decoded to provide remote access to the Siemens Simatic HMI, according to Rios.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...