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.

Attacks/Breaches

6/24/2019
01:00 PM
50%
50%

Raspberry Pi Used in JPL Breach

NASA report shows exfiltration totaling more than 100 GB of information since 2009.

Auditors' reports tend to make for dry reading. But NASA's Inspector General has delivered a report on "Cybersecurity Management and Oversight at the Jet Propulsion Laboratory" that includes twists and turns — like a hacker using a vulnerable, unapproved Raspberry Pi as a doorway into JPL systems.

That Raspberry Pi was responsible for 500 megabytes of NASA Mars mission data leaving JPL servers. The intrusion resulted in an advanced persistent threat (APT) that was active in JPL's network for more than a year before being discovered.

This was the most recent breach listed in the report. Other breaches noted date back to 2009 and include exfiltration totaling more than 100 gigabytes of information. Several of the intrusions feature command-and-control servers with IP addresses located in China, though the responsibility for the latest attack was not assigned to any country or actor.

The Inspector General's report makes a number of suggestions, including greater network segmentation, more rigorous external device approval, and an improved trouble ticket process, for improving cybersecurity at the lab.

Read more here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
tdsan
50%
50%
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
Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
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
CVE-2021-23394
PUBLISHED: 2021-06-13
The package studio-42/elfinder before 2.1.58 are vulnerable to Remote Code Execution (RCE) via execution of PHP code in a .phar file. NOTE: This only applies if the server parses .phar files as PHP.
CVE-2021-34682
PUBLISHED: 2021-06-12
Receita Federal IRPF 2021 1.7 allows a man-in-the-middle attack against the update feature.
CVE-2021-31811
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-31812
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.