Give Me the Green Light Part 1: Hacking Traffic Control Systems
The author uncovers a critical vulnerability in a traffic controller's web interface, allowing unauthorized access to manipulate traffic signals. Vendor response was dismissive, leading to community support and plans for a CVE.
Read original articleThe blog post discusses the author's exploration of vulnerabilities in traffic control systems, starting with responsible disclosure attempts and progressing to finding a critical vulnerability in a web interface of a traffic controller. The vulnerability allowed unauthorized access to the controller without authentication, potentially enabling an attacker to manipulate traffic signals and disrupt the flow of vehicles. Despite reporting the issue to the vendor, the response received was dismissive, citing the product's end-of-life status and implying that the findings were not valid for responsible disclosure. The author decided not to engage further with the vendor and instead shared the experience on LinkedIn, receiving significant support from the community. The post concludes with the author's intention to pursue a CVE for the identified vulnerability and hints at future blog posts exploring traffic controller setups and the significance of authentication bypasses in the context of NTC/IP protocol.
Related
Why I Attack
Nicholas Carlini, a computer science professor, focuses on attacking systems due to a passion for solving puzzles. He categorizes vulnerabilities as patchable or unpatchable, stresses responsible disclosure, and highlights the importance of going public to prevent future exploitation.
CVE-2021-4440: A Linux CNA Case Study
The Linux CNA mishandled CVE-2021-4440 in the 5.10 LTS kernel, causing information leakage and KASLR defeats. The issue affected Debian Bullseye and SUSE's 5.3.18 kernel, resolved in version 5.10.218.
The weirdest QNX bug I've ever encountered
The author encountered a CPU usage bug in a QNX system's 'ps' utility due to a 15-year-old bug. Debugging revealed a race condition, leading to code modifications and a shift towards open-source solutions.
Dev rejects CVE severity, makes his GitHub repo read-only
The 'ip' project's developer, Fedor Indutny, made the GitHub repository read-only due to a disputed CVE report (CVE-2023-42282) about 'node-ip' misidentifying private IP addresses. This incident underscores challenges with inexperienced CVE filings.
The IT Industry is a disaster (2018)
The IT industry faces challenges in IoT and software reliability. Concerns include device trustworthiness, complex systems, and security flaws. Criticisms target coding practices, standards organizations, and propose accountability and skill recognition.
The reality is perhaps even worse than the article suggests. The majority of signal controllers support the NTCIP "standard" MIBs in addition to the "proprietary" MIBs that are provided through FreeTheMIBs. These "standard" MIBs are defined in standards like NTCIP 1202[1], which are freely available online through the NTCIP group.
These standard MIBs let you set/get all kinds of fun settings... put the lights into flash, change timing settings, set "preempts" to give yourself a green light, and more.
The standard also strongly suggests that all vendors use a default SNMP community name of "public". That means, for any traffic controller you happen to find on a network, you can almost certainly change tons of scary settings without even needing to _exploit_ anything!
I've been working in the industry for quite some time, and it's genuinely scary how poorly secured some of this infrastructure is and how slowly things move when issues are found.
(Disclaimer: I work in the industry, not for any of the companies discussed in the article, and all these views are my own and not those of my employer)
[1]: https://www.ntcip.org/file/2019/07/NTCIP-1202v0328A.pdf
Same time, RedThreat's email was kinda (maybe rightly) hostile. Read from the other side it's basically "You have 90 days to work (/maybe pay) me before you start hearing your name on TickTok under the label 'wanna hack the city?'".
"Work with your team" leaves a ton of negotiating opportunity for a company that obviously does this for a living and expects to make money somewhere.
> I requested MIBs from Q-Free but didn’t receive any follow-up after the request and I never received access to the MIBS, so it was back to square one.
Then you go look at https://www.freethemibs.org/advocates and... there they are, "advocates" for free MIB access. What clowns.
The original author of the blog post was invited to speak at an ITSA.ORG conference, and present as through the eyes of an attacker. Thus, the perspective he posits.
There is nothing untoward in his observations but I can see why DefCon might hold off on letting him present his findings.
The ITSA is based in Washington D.C. and has a fairly large membership consisting of state's DOT's (primarily western U.S.), tech companies, car companies, engineering design companies, consulting firms, etc.
Their vision is a better future transformed by transportation technology and innovation. Safer. Greener. Smarter. For all.
A lot of automation is factored into that vision including the use of autonomous vehicles, high-speed inter-connected systems, their attendant technologies, and of course, cyber-security.
Personally, I'm dismayed the U.S. in only now awarding grants for these studies. Maybe the whole thing got sidetracked when our focus shifted to COVID, I don't know. But it does seem as though we're behind the private and governmental initiatives going on in Asia.
2: https://itsa.org/wp-content/uploads/2024/07/Cybersecurity-an...
3: https://itsa.org/wp-content/uploads/2023/01/2026-ITS-America...
Security people act like it's their duty to expose every vulnerability, and that companies are negligent if they don't harden themselves against all attack vectors, while they are responsible for a good part of the danger.
Out in meatspace, I don't wander around picking random people's locks, making smug posts about how vulnerable their houses are (along with their address). Nobody would be happy about that, no matter what color hat I have on.
Security is a twin-engine racket, based on the pillars of
- assumed intellectual superiority
- the actual protection racket part
Related
Why I Attack
Nicholas Carlini, a computer science professor, focuses on attacking systems due to a passion for solving puzzles. He categorizes vulnerabilities as patchable or unpatchable, stresses responsible disclosure, and highlights the importance of going public to prevent future exploitation.
CVE-2021-4440: A Linux CNA Case Study
The Linux CNA mishandled CVE-2021-4440 in the 5.10 LTS kernel, causing information leakage and KASLR defeats. The issue affected Debian Bullseye and SUSE's 5.3.18 kernel, resolved in version 5.10.218.
The weirdest QNX bug I've ever encountered
The author encountered a CPU usage bug in a QNX system's 'ps' utility due to a 15-year-old bug. Debugging revealed a race condition, leading to code modifications and a shift towards open-source solutions.
Dev rejects CVE severity, makes his GitHub repo read-only
The 'ip' project's developer, Fedor Indutny, made the GitHub repository read-only due to a disputed CVE report (CVE-2023-42282) about 'node-ip' misidentifying private IP addresses. This incident underscores challenges with inexperienced CVE filings.
The IT Industry is a disaster (2018)
The IT industry faces challenges in IoT and software reliability. Concerns include device trustworthiness, complex systems, and security flaws. Criticisms target coding practices, standards organizations, and propose accountability and skill recognition.