Monday, April 7, 2025
HomeComputer SecurityNASA Data Leak - Internal App Leaked NASA Staff and Project Sensitive...

NASA Data Leak – Internal App Leaked NASA Staff and Project Sensitive data

Published on

SIEM as a Service

Follow Us on Google News

A erious Misconfiguration flaw that discovered in NASA internal App JIRA leaked sensitive internal data to the public and anyone can access the exposed data.

JIRA is a project management system that powered by Atlassian that allows bug tracking and agile project management.

Leaked data contains very sensitive information including internal user details, project details, employee names, employees mail id .

- Advertisement - Google News

An uncovered misconfiguration with couple of settings in JIRA system that deployed within the NASA network to manage the employees and project information.

It allow any one in the internet can able to access the NASA internal data and also it provide an application access to cyber criminals.

A researcher who have been discovered this serious flaw in NASA internal system reported that the issue was due to the wrong permissions assigned to them.

The process of applying a filter in the dashboard that gives access to an internal employee when setting the visibility to “All users” and “Everyone” respectively.

But this misconfiguration flaw allows the data to share everyone on the public that means everyone can access to the NASA internal data.

Along with this, public users can change the functionality in Jira to gain complete list of employees user name and password.

According to Researcher, This information disclosure is the result of an authorization misconfiguration in Jira’s Global Permissions settings. Because of the wrong permissions scheme, the following internal information appeared to be vulnerable:

  • all account’s employees’ names and emails,
  • employees’ roles through JIRA groups,
  • current projects, upcoming milestones through JIRA dashboards/filters.

NASA Exposed Data

Using this Misconfiguration flaw, he found the complete list of every NASA user’s username and email address by using a JIRA picker functionality, Also he shared a screenshot (first line) there are in total of 1000 NASA internal user details.

” Additionally, it can give an attacker an idea of what kind of information may be housed within the application and what projects team is working upon along with showing features of different projects. Researcher said,.

During this exploitation research, he was able to access some of the highly sensitive information of NASA such as internal user details, project details, employee names, employees mail id etc.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity updates also you can take the Best Cybersecurity courses online to keep your self-updated.

Also Read: NASA Hacked – Hackers Compromised NASA Servers & Personal Data May have been Stolen

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Threat Actors Exploit Fake CAPTCHAs and Cloudflare Turnstile to Distribute LegionLoader

In a sophisticated attack targeting individuals searching for PDF documents online, cybercriminals are using...

HellCat, Rey, and Grep Groups Dispute Claims in Orange and HighWire Press Cases

SuspectFile.com has uncovered a complex web of overlapping claims and accusations within the cybercrime...

AI Surpasses Elite Red Teams in Crafting Effective Spear Phishing Attacks

In a groundbreaking development in the field of cybersecurity, AI has reached a pivotal...

Threat Actors Use Windows Screensaver Files as Malware Delivery Method

Cybersecurity experts at Symantec have uncovered a sophisticated phishing campaign targeting various sectors across...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Threat Actors Exploit Fake CAPTCHAs and Cloudflare Turnstile to Distribute LegionLoader

In a sophisticated attack targeting individuals searching for PDF documents online, cybercriminals are using...

HellCat, Rey, and Grep Groups Dispute Claims in Orange and HighWire Press Cases

SuspectFile.com has uncovered a complex web of overlapping claims and accusations within the cybercrime...

AI Surpasses Elite Red Teams in Crafting Effective Spear Phishing Attacks

In a groundbreaking development in the field of cybersecurity, AI has reached a pivotal...