Skip to main content

I'll have a Gamma Frappuccino, please.


A recent story has been making the rounds: "Hundreds of Nuclear Radiation Monitors Were Allegedly Hacked by Former Repairmen".  Basically, it seems that more than a year ago  two disgruntled employees sabotaged +300 radiation monitoring devices, which were part of a nation-wide civil radiation monitoring network (RAR) in Spain. On top of that, they were apparently using the free WiFi of a Starbucks to carry out their activities. Obviously not being the sharpest tool in the box they were eventually caught.

In this story there is a boring part, which is everything related to these guys and their motivations, and a slightly more interesting part which is the underlying technology behind Radiation Monitoring Networks (RMN).

In 2017 I presented at BlackHat USA 'Go Nuclear: Breaking Radiation Monitoring Devices", so I thought  it could be interesting to write a brief post to provide some context.

The NeverEnding story

As in most 'disgruntled employee' attacks, the initial motivation behind the sabotage seems to be a 'poorly assessed' reaction to a troubled employment relationship. 

According to the information publicly released by the police the attacks started on March 2021. Coincidentally, by using the public procurement portal of the Spanish State, we can find that, in 2020, a public contract to support and maintain the RAR network was announced, as the valid one at that time was about to expire in Feb 2021.  

Anyway, if you're interested in the technology,  public procurement documents always provide a lot of information when you are researching into nation-wide systems. As expected, it is possible to find some interesting bits of information about the RAR network, including its topology, devices, deployments...


The radiation monitoring devices are provided by Envinet. Indra seems to have developed some Data Acquisition Units as well as the Control System.

Sensor Units - Envinet

Data Acquisition Units - Indra


A simple search provides some additional information about these DTUs.

https://www.indracompany.com/sites/default/files/dtu_0.pdf

This also seems to match with some  documents from Envinet


If we take a look at the location of the sensor deployments, provided in the procurement document  (Page 23), and map them to a Shodan search for Envinet devices, almost no one is going to be surprised by the fact that, at least, 22 stations of the RAR network were recently exposed to the Internet. For instance, in the image below, we are mapping the station identified  by 'ESCALONA' (a small town in Toledo, a province of Spain), to an Envinet device geo-located to 'El Casar de Escalona', a small town in the same province.



I think we have had enough from the RAR network; a civil network with some legacy devices where, I assume, a questionable password policy is in place. In addition to this, it is likely maintained by a chain of contractors...

Fortunately, as in any other system supporting safety operations, there is no single point of failure so even if the entire RAR network had been wiped out, other networks would have noticed if something really bad was going on.

So the most interesting thing so far is how ubiquitous Envinet systems are (shodan also provides a glimpse into Envinet's NMC system), especially in Europe, but also world-wide. As a result, Envinet products and devices seem to be an interesting target.



Attacking Radiation Monitoring Devices

Radioactivity is invisible for the human eye so, as in many other industrial processes, we're essentially relying on the output from a system able to analyze, on our behalf, what is going on in our environment.

Thus, in the context of Radiation Monitoring Instruments,  their 'output' will have two main purposes:

1.- Provide data to be consumed by operators

2.- Provide inputs to safety systems

As a result, when I was researching into RMN five years ago, I mainly focused on just two kinds of attacks, which are outlined below. It is important to note that in both cases, the motivation for performing the attack is pretty extreme, so we would be essentially talking about scenarios derived from 'profound conflicts' between nation-states or  sophisticated terrorist attacks.

1. - Hide what is happening

By far, this first scenario is usually the worst, as we have to assume the attackers are trying to hide abnormal radiation levels, so we would be  already facing a pretty bad ongoing situation. This secondary attack against the RMN would be only aimed to increase the impact of the primary attack.  

However, there are some other scenarios, where someone would want to hide abnormal radiation levels just transiently, for instance in radioactive material smuggling scenarios.

Back in 2017, I looked into some of the Radiation Portal Monitors deployed at US borders, checkpoints or secure facilities, finding backdoors, insecure protocols and the usual stuff.

In addition to borders and ports, Nuclear Power Plants (NPP) are the most common facilities where RMDs are found.  However, if a malicious actor is trying to hide abnormal radiation levels in a NPP, quite a few systems need to be compromised.  

https://www.blackhat.com/docs/us-17/wednesday/us-17-Santamarta-Go-Nuclear-Breaking%20Radition-Monitoring-Devices-wp.pdf (Page 13)

Therefore, a real-world attack against RMDs in a NPP would likely lie in the next scenario instead.

2. - Show what is not happening

This scenario covers those attacks whose nature is primarily 'cyber'. As I mentioned before, when talking about radiation, our assessment of the situation highly depends on a Radiation Monitoring Instrument's output.

If you can control that output, you could potentially trigger a response that does not correspond to the actual conditions the system is operating at. For instance, in the context of a NPP, the implications of this scenario can be divided in:

- How humans will behave according to the information they are getting 

When the operators are reacting to falsified radioactive leakage alarms according to the defined Emergency Action Levels. (i.e Three Mile island incident)

- How safety systems (Class 1E) will react

These systems are provided to ensure the safe shutdown of the reactor or residual heat removal, or to limit the consequences of anticipated operational occurrences.

Final thoughts 

In 2017, I  managed to compromise the RF security scheme used in RMDs from Mirion, based on Digi's XBEE. This attack allowed to forge arbitrary radiation readings, thus enabling the attackers with the ability to implement some of attacks covered in the scenarios we have been discussing.

https://www.blackhat.com/docs/us-17/wednesday/us-17-Santamarta-Go-Nuclear-Breaking%20Radition-Monitoring-Devices.pdf (Slide 18)

In general terms, we should also assume that most of the commercial RMDs out there, and their corresponding networks, are probably an easy target for malicious actors with a strong motivation and plenty of resources.

Although, technically, two guys at a Starbucks disabling the communication of a civil Radiation Monitoring Network endangers the ability to detect if something bad is going on,  it may seem worse than it actually is. 

On the other hand, I think that the worst-case attack scenarios against this kind of networks are those intended to falsify the 'reality', thus tricking the victim (either operators or safety systems) into triggering a predefined procedure (i.e shutting down a reactor) which has been designed for different conditions.

























Popular posts from this blog

SATCOM terminals under attack in Europe: a plausible analysis.

------ Update 03/12/2022 Reuters has published new information on this incident, which initially matches the proposed scenario. You can find the  update  at the bottom of this post. ------ February 24th: at the same time Russia initiated a full-scale attack on Ukraine, tens of thousands of KA-SAT SATCOM terminals suddenly  stopped  working in several european countries: Germany, Ukraine, Greece, Hungary, Poland...Germany's Enercon moved forward and acknowledged that approximately 5800 of its wind turbines, presumably those remotely operated via a SATCOM link in central Europe, had lost contact with their  SCADA server .  In the affected countries, a significant part of the customers of Eutelsat's domestic broadband service were also unable to access Internet.  From the very beginning Eutelsat and its parent company Viasat, stated that the issue was being investigated as a cyberattack. Since then, details have been scarcely provided but few days ago I came across a really inter

VIASAT incident: from speculation to technical details.

  34 days after the incident, yesterday Viasat published a statement providing some technical details about the attack that affected tens of thousands of its SATCOM terminals. Also yesterday, I eventually had access to two Surfbeam2 modems: one was targeted during the attack and the other was in a working condition. Thank you so much to the person who disinterestedly donated the attacked modem. I've been closely covering this issue since the beginning, providing a  plausible theory based on the information that was available at that time, and my experience in this field. Actually, it seems that this theory was pretty close to what really happened. Fortunately, now we can move from just pure speculation into something more tangible, so I dumped the flash memory for both modems (Spansion S29GL256P90TFCR2 ) and the differences were pretty clear. In the following picture you can see 'attacked1.bin', which belongs to the targeted modem and 'fw_fixed.bin', coming from t

Reversing 'France Identité': the new French digital ID.

  -------------- Update from 06/10/2023 : following my publication, I’ve been in contact with France Identité CISO and they could provide more information on the measures they have taken in the light of these findings: We would like to thank you for your in-depth technical research work on “France Identite” app that was launched in beta a year ago and for which you were rewarded. As you know, the app is now generally available on iOS and Android through their respective app stores. Your work, alongside French cybersecurity agency (ANSSI) research, made us update and modify deeply the E2EE Secure Channel used between the app and our backend. It is now mostly based on TLS1.3. Those modifications were released only a few weeks after you submitted your work through our private BugBounty program with YesWeHack. That released version also fixes the three other vulnerabilities you submitted. From the beginning of “France Identite” program, it was decided to implicate cybersecurity community,