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-54376: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in SpectoLabs hoverfly

0
High
VulnerabilityCVE-2025-54376cvecve-2025-54376cwe-200cwe-287
Published: Wed Sep 10 2025 (09/10/2025, 19:49:08 UTC)
Source: CVE Database V5
Vendor/Project: SpectoLabs
Product: hoverfly

Description

Hoverfly is an open source API simulation tool. In versions 1.11.3 and prior, Hoverfly’s admin WebSocket endpoint /api/v2/ws/logs is not protected by the same authentication middleware that guards the REST admin API. Consequently, an unauthenticated remote attacker can stream real-time application logs (information disclosure) and/or gain insight into internal file paths, request/response bodies, and other potentially sensitive data emitted in logs. Version 1.12.0 contains a fix for the issue.

AI-Powered Analysis

AILast updated: 09/10/2025, 20:15:38 UTC

Technical Analysis

CVE-2025-54376 is a high-severity vulnerability affecting SpectoLabs' open source API simulation tool, Hoverfly, specifically versions prior to 1.12.0. The vulnerability arises because the admin WebSocket endpoint /api/v2/ws/logs lacks the authentication middleware that protects the REST admin API endpoints. This design flaw allows unauthenticated remote attackers to connect to the WebSocket endpoint and stream real-time application logs. These logs may contain sensitive information such as internal file paths, request and response bodies, and other data that could aid attackers in reconnaissance or further exploitation. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information) and CWE-287 (Improper Authentication). The CVSS 4.0 base score is 7.8, reflecting a high severity due to the network attack vector, no required privileges or user interaction, and a high impact on confidentiality. Although no known exploits are currently in the wild, the ease of exploitation and the sensitive nature of the leaked data make this a significant risk. The issue was addressed in Hoverfly version 1.12.0 by adding proper authentication controls to the WebSocket admin endpoint, aligning it with the protections on the REST API.

Potential Impact

For European organizations using Hoverfly for API simulation and testing, this vulnerability could lead to unauthorized disclosure of sensitive internal information. Exposure of application logs can reveal internal architecture details, API request and response data, and potentially sensitive business or user data. This information leakage can facilitate further attacks such as targeted phishing, exploitation of other vulnerabilities, or lateral movement within networks. Since Hoverfly is often used in development, testing, and staging environments, the impact might extend beyond production systems if these environments are connected to internal networks. Confidentiality is primarily impacted, but integrity and availability are less directly affected. The risk is heightened for organizations in regulated sectors (e.g., finance, healthcare, telecommunications) where data privacy is critical and compliance with GDPR and other regulations is mandatory. Unauthorized access to logs could also expose personal data, leading to regulatory penalties and reputational damage.

Mitigation Recommendations

European organizations should immediately upgrade Hoverfly to version 1.12.0 or later to ensure the WebSocket admin endpoint is properly secured with authentication middleware. Until the upgrade is applied, organizations should restrict network access to the Hoverfly admin interface using network segmentation, firewall rules, or VPNs to limit exposure to trusted users only. Monitoring and logging access to the admin endpoints should be enhanced to detect any unauthorized connection attempts. Additionally, organizations should review the contents of logs exposed via the WebSocket endpoint and sanitize or minimize sensitive information logged during API simulation. Implementing role-based access controls (RBAC) and enforcing strong authentication mechanisms for all admin interfaces is recommended. Finally, security teams should conduct audits of development and testing environments to ensure that similar misconfigurations do not exist elsewhere.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-07-21T16:12:20.733Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68c1d8ec12193b50d3fff70c

Added to database: 9/10/2025, 8:00:44 PM

Last enriched: 9/10/2025, 8:15:38 PM

Last updated: 10/30/2025, 8:58:38 AM

Views: 100

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