Author Topic: NASA Spacecraft was hackable for years until AI found it  (Read 14 times)

0 Members and 1 Guest are viewing this topic.

Offline Buster's Uncle

  • Geo's kind, I unwind, HE'S the
  • Planetary Overmind
  • *
  • Posts: 53540
  • €507
  • View Inventory
  • Send /Gift
  • Because there are times when people just need a cute puppy  Soft kitty, warm kitty, little ball of fur  A WONDERFUL concept, Unity - & a 1-way trip that cost 400 trillion & 40 yrs.  
  • AC2 is my instrument, my heart, as I play my song.
  • Planet tales writer Smilie Artist Custom Faction Modder AC2 Wiki contributor Downloads Contributor
    • View Profile
    • My Custom Factions
    • Awards
NASA Spacecraft was hackable for years until AI found it
« on: December 11, 2025, 03:58:09 pm »
GEEKSPIN
NASA Spacecraft was hackable for years until AI found it
A 3-year-old vulnerability in NASA’s communications layer went unnoticed until AI exposed the cracks in manual review
Stefan Milovanovic
Wed, December 10, 2025 at 11:30 AM EST
3 min read



NASA's Deep Space Station 35 (DSS-35) at the Canberra Deep Space Communication Complex in Tidbinbilla, Australia, photographed on May 21, 2014 | ©Image Credit: NASA


Even with rigorous protocols and billion-dollar budgets, human oversight has its limits—a reality NASA was forced to confront this week. After three years of manual reviews failing to catch a critical flaw in the agency’s communications software, an AI tool from startup AISLE identified the vulnerability in a matter of days.

The flaw sat inside CryptoLib, the cryptographic library NASA uses to authenticate commands traveling between Earth and its spacecraft. No one caught it — not during reviews, not during updates — until the automated analysis flagged the specific lines of code that human eyes had missed.

In a blog post dedicated to outlining the findings, AISLE described the issue as follows: “For three years, the security system meant to protect spacecraft-to-ground communications contained a vulnerability that could undermine that protection.”

The startup’s researchers warned that such a vulnerability poses a direct threat to the billions of dollars invested in space infrastructure and the scientific missions they support.


The Authentication Gap

The weak spot lived inside the authentication setup. If an attacker managed to get hold of operator credentials — phishing, malware, the usual playbook — the door opened wider than anyone expected.

Researchers described the flaw as one that “transforms what should be routine authentication configuration into a weapon,” warning that it lets attackers “inject arbitrary commands that execute with full system privileges.”

To execute such commands, however, local access would still have been required, meaning this wasn’t a remote takeover scenario. But for systems tied to active missions, that distinction only goes so far. The flaw reportedly survived several human reviews over its lifespan before AISLE’s autonomous analyzer surfaced it and guided a fix in four days.


The Case for Automation

This shift towards automation comes as NASA’s operational landscape becomes increasingly complex, blending aging legacy hardware with decentralized ground controls.

Just last month, the Mars Reconnaissance Orbiter—which has been circling the Red Planet since 2006—relied on a newly developed “very large roll” maneuver to debunk a sub-surface lake hypothesis. That operation required precise software commands to rotate the aging spacecraft 120 degrees mid-orbit, a feat that demonstrates how deeply new code must interact with decades-old hardware.

Simultaneously, the agency is preparing for the ESCAPADE mission, where mission control will be handed over to UC Berkeley rather than NASA’s traditional hubs. With universities and private partners like Rocket Lab now managing active spacecraft, the network of “ground control” access points is expanding, creating a wider surface area for the kind of authentication vulnerabilities identified in CryptoLib.

NASA’s codebases have expanded over decades of missions, creating a complexity that AISLE’s researchers argue makes tools like theirs increasingly necessary as mission software grows older, larger, and more interconnected.

They noted that “Human review remains valuable, but autonomous analyzers can systematically examine entire codebases, flag suspicious patterns, and operate continuously as code evolves.”

Although AISLE didn’t report any evidence that the vulnerability was used in the wild, this episode adds to a growing list of reminders that spacecraft security now depends as much on software hygiene as it does on ground control protocols. And that even code written to keep things safe can carry problems no one notices until a machine points straight at them.

Sources: Space.com, CVE, Daily Star, Aisle

Read the original article on GEEKSPIN.

 

* User

Welcome, Guest. Please login or register.
Did you miss your activation email?


Login with username, password and session length

Select language:

* Community poll

SMAC v.4 SMAX v.2 (or previous versions)
-=-
24 (7%)
XP Compatibility patch
-=-
9 (2%)
Gog version for Windows
-=-
106 (33%)
Scient (unofficial) patch
-=-
40 (12%)
Kyrub's latest patch
-=-
14 (4%)
Yitzi's latest patch
-=-
89 (28%)
AC for Mac
-=-
3 (0%)
AC for Linux
-=-
5 (1%)
Gog version for Mac
-=-
10 (3%)
No patch
-=-
16 (5%)
Total Members Voted: 316
AC2 Wiki Logo
-click pic for wik-

* Random quote

Imagine the entire contents of the planetary datalinks, the sum total of human knowledge, blasted into the Planetmind's fragile neural network with the full force of every reactor on the planet. That is our last-ditch attempt to win humanity a reprieve from extinction at the hands of an awakened alien god.
~Academician Prokhor Zakharov 'Planet Speaks'

* Select your theme

*
Templates: 5: index (default), PortaMx/Mainindex (default), PortaMx/Frames (default), Display (default), GenericControls (default).
Sub templates: 8: init, html_above, body_above, portamx_above, main, portamx_below, body_below, html_below.
Language files: 4: index+Modifications.english (default), TopicRating/.english (default), PortaMx/PortaMx.english (default), OharaYTEmbed.english (default).
Style sheets: 0: .
Files included: 47 - 1280KB. (show)
Queries used: 41.

[Show Queries]