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
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


COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25514
PUBLISHED: 2020-09-22
Sourcecodester Simple Library Management System 1.0 is affected by Incorrect Access Control via the Login Panel, http://&lt;site&gt;/lms/admin.php.
CVE-2020-25515
PUBLISHED: 2020-09-22
Sourcecodester Simple Library Management System 1.0 is affected by Insecure Permissions via Books &gt; New Book , http://&lt;site&gt;/lms/index.php?page=books.
CVE-2020-14022
PUBLISHED: 2020-09-22
Ozeki NG SMS Gateway 4.17.1 through 4.17.6 does not check the file type when bulk importing new contacts (&quot;Import Contacts&quot; functionality) from a file. It is possible to upload an executable or .bat file that can be executed with the help of a functionality (E.g. the &quot;Application Star...
CVE-2020-14023
PUBLISHED: 2020-09-22
Ozeki NG SMS Gateway through 4.17.6 allows SSRF via SMS WCF or RSS To SMS.
CVE-2020-14024
PUBLISHED: 2020-09-22
Ozeki NG SMS Gateway through 4.17.6 has multiple authenticated stored and/or reflected XSS vulnerabilities via the (1) Receiver or Recipient field in the Mailbox feature, (2) OZFORM_GROUPNAME field in the Group configuration of addresses, (3) listname field in the Defining address lists configuratio...