Slashdot Mirror


Researchers Discover Critical Security Flaws Found In Nuke Plant Radiation Monitors (securityweek.com)

wiredmikey writes from a report via Security Week: Researchers have discovered multiple unpatched vulnerabilities in radiation monitoring devices that could be leveraged by attackers to reduce personnel safety, delay detection of radiation leaks, or help international smuggling of radioactive material. Ruben Santamarta, a security consultant at Seattle-based IOActive, at the Black Hat conference on Wednesday, saying that radiation monitors supplied by Ludlum, Mirion and Digi contain multiple vulnerabilities. There are many kinds of radiation monitors used in many different environments. IOActive concentrated its research on portal monitors, used at airports and seaports; and area monitors, used at Nuclear Power Plants (NPPs). However, little effort was required for the portal monitors: "the initial analysis revealed a complete lack of security in these devices, so further testing wasn't necessary to identify significant vulnerabilities," Santamarta explained in his report (PDF). In the Ludlum Model 53 personnel portal, IOActive found a backdoor password, which could be used to bypass authentication and take control of the device, preventing the triggering of proper alarms.

2 of 43 comments (clear)

  1. Not at all suprising by ScienceBard · · Score: 5, Informative

    I work alongside a team that maintains and repairs these things, and they certainly aren't made for high levels of digital security. If you know the right place to stick a flash drive in a portal monitor sure you could do damage to it, I can attest it isn't fancy. But it doesn't have to be.

    For one, a portal monitor is a last line of defense against radioactive contamination being tracked around. We aren't talking about huge levels of radiation, the contamination is managed by good safety practices (work plans, electronic dosimeters, maps of potential loose contamination, etc.). But there is a responsibility to ensure that a worker doesn't accidentally drag anything home with them to the general public, no matter how insignificant. Which is really what the monitors are for.

    For two, there are usually multiples of these things in a row, inside a heavily fortified concrete area surrounded by unfriendly looking men with machine guns (at least at any nuclear facility, a school or small lab that has one would be different). Combine those two things, and an attempt to "hack" monitors would be about the most moronic waste of resources any government would ever spend. You couldn't do any real damage, you couldn't hurt anyone... at best you could get a radiation protection manager fired for allowing a small uncontrolled release of radioactivity, or a miscalculated dose rate to a worker.

    I'm all for security, but there needs to be a little perspective. Standalone portal monitors that are airgaped don't need to be a digital fort knox. The level of effort is extreme to screw with them, and the payback would be insignificant. The truth is most specialized lab/nuclear equipment isn't extremely secure unless it serves an actual security function (a CDA, critical digital asset, which are almost always network isolated and have more robust security). Quite the opposite, most of it is very simple and made to be maintained almost indefinitely by moderately skilled technicians. Cost, usability, and maintainability is more important.

    1. Re:Not at all suprising by arglebargle_xiv · · Score: 3, Informative

      Vaguely similar position, I've looked at the code running in some of these things. It's written by nuclear physicists who by the looks of the code are often self-taught programmers. It's not just a lack of security in there, it's a lack of any kind of sound programming practice. The physics part (meaning the algorithms and analysis portion) is just fine, but the code itself is ghastly, it's a wonder it works at all in some cases. If you move any part of it outside the parameters under which it was written, anything can happen, endless loops, processing invalid data, reading/writing arbitrary memory locations, you name it.

      It's known that these things have approximately zero security. They were accessed via VPN boxes that went back to a central, secure, location, and physical security around them was very, very heavy. If you know what you're dealing with, you can institute appropriate security measures to address it.