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.

Comments
Raspberry Pi Used in JPL Breach
Newest First  |  Oldest First  |  Threaded View
tdsan
tdsan,
User Rank: Ninja
6/27/2019 | 9:16:06 PM
Identified and found numerous security vulnerabilities
We also found that security problem log tickets, created in the ITSDB when a potential or actual IT system security vulnerability is identified, were not resolved for extended periods of time—sometimes longer than 180 days.
However, we found the database inventory incomplete and inaccurate, placing at risk JPL's ability to effectively monitor, report, and respond to security incidents.
Further, we found that JPL's network gateway that controls partner access to a shared IT environment for specific missions and data had not been properly segmented to limit users only to those systems and applications for which they had approved access.
PL had not implemented a threat hunting program recommended by IT security experts to aggressively pursue abnormal activity on its systems for signs of compromise, and instead rely on an ad hoc process to search for intruders.
We found that multiple JPL incident management and response practices deviate from NASA and recommended industry practices.For example, unlike NASA's Security Operations Center (SOC), JPL's SOC does not maintain round-the-clock availability of IT security incident responders and JPL's incident response plan does not include all federally-recommended elements.
In addition, team coordination issues delayed completion of incident containment and eradication steps for the April 2018 incident.
No controls were in place to ensure JPL compliance with this requirement nor did NASA officials have access to JPL's incident management system.
As of March 2019, the Agency had not approved JPL's plans to implement new IT security policies and requirements NASA included in its October 2018 contract.

From looking at the report, the JPL Raspberry PI was just one item that was a major issue, I think where I am confused is how did a device from the public get on the network of NASA's Jet Propulsion system's network? There should have been some sort of notification that looked up MAC addresses that were purchased or perform a reg-ex lookup of mac addresses that are not on the production network's device purchase list.
MAC Address/OUIVendor
B8:27:EB Raspberry Pi Foundation
Cisco Network - show mac address-table | in b8:27:eb
show ip arp vlan <vlan no> | include b827.eb

This is from NASA's final security report - https://oig.nasa.gov/docs/IG-19-022.pdf. They stated this occurred over the last 10 years. I am not sure about the rest of the group but the contract, employees and the rest of the security department should all be fired from this point (start from the top, remove everyone and start again).

This is what I mean by incompentence at the highest level.

Todd S


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Promise and Reality of Cloud Security
Cloud security has been part of the cybersecurity conversation for years but has been on the sidelines for most enterprises. The shift to remote work during the COVID-19 pandemic and digital transformation projects have moved cloud infrastructure front-and-center as enterprises address the associated security risks. This report - a compilation of cutting-edge Black Hat research, in-depth Omdia analysis, and comprehensive Dark Reading reporting - explores how cloud security is rapidly evolving.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-23119
PUBLISHED: 2023-02-02
The use of the cyclic redundancy check (CRC) algorithm for integrity check during firmware update makes Ubiquiti airFiber AF2X Radio firmware version 3.2.2 and earlier vulnerable to firmware modification attacks. An attacker can conduct a man-in-the-middle (MITM) attack to modify the new firmware im...
CVE-2023-23120
PUBLISHED: 2023-02-02
The use of the cyclic redundancy check (CRC) algorithm for integrity check during firmware update makes TRENDnet TV-IP651WI Network Camera firmware version v1.07.01 and earlier vulnerable to firmware modification attacks. An attacker can conduct a man-in-the-middle (MITM) attack to modify the new fi...
CVE-2023-0651
PUBLISHED: 2023-02-02
A vulnerability was found in FastCMS 0.1.0. It has been classified as critical. Affected is an unknown function of the component Template Management. The manipulation leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be u...
CVE-2023-23110
PUBLISHED: 2023-02-02
An exploitable firmware modification vulnerability was discovered in certain Netgear products. The data integrity of the uploaded firmware image is ensured with a fixed checksum number. Therefore, an attacker can conduct a MITM attack to modify the user-uploaded firmware image and bypass the checksu...
CVE-2023-0650
PUBLISHED: 2023-02-02
A vulnerability was found in YAFNET up to 3.1.11 and classified as problematic. This issue affects some unknown processing of the component Signature Handler. The manipulation leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be...