Saturday, December 28, 2024
HomeCyber Security NewsHonda Data Leak - 134 Million Documents Related to Internal Network and...

Honda Data Leak – 134 Million Documents Related to Internal Network and Computers Leaked

Published on

SIEM as a Service

An unsecured ElasticSearch database belongs to largets automobile manufacturer exposed online. The exposed documents include internal network and computers data of Honda Motor Company.

Security researcher Justin Paine uncovered the leaked database, the ElasticSearch database contains 134M that worth around 40GB of data. It appears the database publically available for more than a week.

The unprotected database contains sensitive information such as “hostname, MAC address, internal IP, operating system version, which patches had been applied, hostnames and the status of Honda’s endpoint security software.”

- Advertisement - SIEM as a Service

Exposed data

The databases contain dealership information and the data related to Honda’s global network of employee machines. It exposes the names of endpoint security vendor networks that protect Honda’s machines and the high-level employee’s data such as CEO, CFO, CSO, etc.

By having the unique data attackers can launch targeted attacks and can exploit the vulnerability to get access over the network and to penetrate further.

A table in name “ad_com_all” exposes the OS versions, hostnames and has over 300,000 data points, another table spotted has employee name, department, last login, employee number and account names.

Paine also identified several tables that include the employee email, department, machine IP address, MAC address, hostname, operating system, machine type, endpoint security state, printer name, internal I Pand which Windows KB/patches.

Also, the leaks include the “CEO’s full email, full name, department, MAC address, which Windows KB/patches had been applied, OS, OS version, endpoint security status, IP, and device type.”

Paine reached out to Honda’s security team on July 6th and the ElasticSearch database was secured, here is the statement from Honda.

“Thank you very much for pointing out the vulnerability. The security issue you identified could have potentially allowed outside parties to access some of Honda’s cloud-based data that consisted of information related to our employees and their computers. We investigated the system’s access logs and found no signs of data download by any third parties. At this moment, there is no evidence that data was leaked, excluding the screenshots taken by you. We will take appropriate actions by relevant laws and regulations, and will continue to work on proactive security measures to prevent similar incidents in the future.”

You can follow us on Linkedin, Twitter, Facebook for daily Cybersecurity updates also you can take the Best Cybersecurity course online to keep yourself updated.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Lumma Stealer Attacking Users To Steal Login Credentials From Browsers

Researchers observed Lumma Stealer activity across multiple online samples, including PowerShell scripts and a...

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...

Palo Alto Networks Vulnerability Puts Firewalls at Risk of DoS Attacks

A critical vulnerability, CVE-2024-3393, has been identified in the DNS Security feature of Palo...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Lumma Stealer Attacking Users To Steal Login Credentials From Browsers

Researchers observed Lumma Stealer activity across multiple online samples, including PowerShell scripts and a...

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...