Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-41109: CWE-798 Use of Hard-coded Credentials in Ghost Robotics Vision 60

0
High
VulnerabilityCVE-2025-41109cvecve-2025-41109cwe-798
Published: Wed Oct 22 2025 (10/22/2025, 08:15:42 UTC)
Source: CVE Database V5
Vendor/Project: Ghost Robotics
Product: Vision 60

Description

Ghost Robotics Vision 60 v0.27.2 includes, among its physical interfaces, three RJ45 connectors and a USB Type-C port. The vulnerability is due to the lack of authentication mechanisms when establishing connections through these ports. Specifically, with regard to network connectivity, the robot's internal router automatically assigns IP addresses to any device physically connected to it. An attacker could connect a WiFi access point under their control to gain access to the robot's network without needing the credentials for the deployed network. Once inside, the attacker can monitor all its data, as the robot runs on ROS 2 without authentication by default.

AI-Powered Analysis

AILast updated: 10/29/2025, 09:04:02 UTC

Technical Analysis

The vulnerability CVE-2025-41109 affects Ghost Robotics Vision 60 version 0.27.2 and is classified under CWE-798, indicating the use of hard-coded credentials or insufficient authentication mechanisms. The robot exposes three RJ45 Ethernet ports and a USB Type-C port, all of which lack proper authentication controls. Its internal router automatically assigns IP addresses to any device physically connected, allowing an attacker to connect a rogue WiFi access point or other network device without needing valid credentials. Once connected, the attacker gains access to the robot’s internal network, which runs Robot Operating System 2 (ROS 2). ROS 2 by default does not enforce authentication, meaning the attacker can monitor, intercept, or manipulate data and commands transmitted within the robot’s network. This creates a significant risk of unauthorized control or data leakage. The vulnerability arises because the robot’s network interfaces trust any connected device implicitly, and the lack of authentication on ROS 2 exacerbates the risk. Exploitation requires physical access to the robot’s ports but no prior authentication or user interaction. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H) indicates a high-severity issue with low attack complexity and no privileges or user interaction required, impacting confidentiality, integrity, and availability severely. No known exploits are currently in the wild, but the risk is significant given the robot’s deployment in sensitive environments.

Potential Impact

For European organizations deploying Ghost Robotics Vision 60, this vulnerability poses a substantial risk. Attackers with physical access can infiltrate the robot’s network, leading to potential espionage, data theft, or sabotage of robotic operations. This is particularly critical in sectors such as defense, industrial automation, research institutions, and critical infrastructure where these robots may be used. The lack of authentication on network interfaces and ROS 2 communications can allow attackers to manipulate robot behavior, disrupt missions, or exfiltrate sensitive data. The automatic IP assignment to any connected device increases the attack surface, making physical security paramount. Compromise could lead to loss of operational integrity, safety hazards, and reputational damage. Additionally, the vulnerability could be exploited as a pivot point to access broader organizational networks if proper network segmentation is not enforced. The high CVSS score reflects the severity and potential widespread impact on confidentiality, integrity, and availability of robotic systems.

Mitigation Recommendations

To mitigate this vulnerability, organizations should: 1) Physically secure all Ghost Robotics Vision 60 units to prevent unauthorized access to RJ45 and USB Type-C ports. 2) Disable or restrict unused physical interfaces to reduce attack vectors. 3) Implement network segmentation to isolate the robot’s internal network from broader organizational networks, preventing lateral movement. 4) Enforce strong authentication and access control mechanisms on all network interfaces and ROS 2 communications, potentially by configuring ROS 2 security features such as DDS Security plugins. 5) Monitor network traffic for unauthorized devices or anomalous connections on robot interfaces. 6) Regularly update the robot’s firmware and software once patches addressing this vulnerability become available from Ghost Robotics. 7) Employ intrusion detection systems tailored to robotic network protocols to detect exploitation attempts. 8) Conduct security audits and penetration testing focused on physical and network access controls of robotic platforms. These steps go beyond generic advice by focusing on physical interface security, ROS 2 authentication, and network architecture hardening specific to this robot’s design.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
INCIBE
Date Reserved
2025-04-16T09:09:39.343Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68f8942ad59611fbd95e690a

Added to database: 10/22/2025, 8:22:02 AM

Last enriched: 10/29/2025, 9:04:02 AM

Last updated: 12/6/2025, 9:30:25 PM

Views: 99

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats