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-2024-45258: n/a

0
Critical
VulnerabilityCVE-2024-45258cvecve-2024-45258
Published: Sun Aug 25 2024 (08/25/2024, 00:00:00 UTC)
Source: CVE Database V5

Description

CVE-2024-45258 is a critical vulnerability in the Go 'req' package versions before 3. 43. 4, where malformed URLs can cause the package to send unintended HTTP requests. This occurs due to the 'cleanHost' function in http. go using a 'garbage in, garbage out' approach, failing to properly validate or sanitize input URLs. The vulnerability has a CVSS score of 9. 8, indicating high impact on confidentiality, integrity, and availability without requiring authentication or user interaction. Exploitation could lead to unauthorized data exposure, request forgery, or denial of service. No known exploits are currently reported in the wild. Organizations using the vulnerable versions of the 'req' package in Go should prioritize updating to version 3.

AI-Powered Analysis

AILast updated: 02/26/2026, 08:12:00 UTC

Technical Analysis

CVE-2024-45258 is a critical vulnerability identified in the 'req' package for the Go programming language, affecting all versions prior to 3.43.4. The root cause lies in the 'cleanHost' function within the http.go source file, which employs a 'garbage in, garbage out' design philosophy. This means that when a malformed URL is provided to the package, it does not adequately sanitize or validate the input, resulting in the possibility of sending unintended HTTP requests. Such behavior can lead to multiple security issues including unauthorized data leakage, cross-site request forgery, or denial of service conditions. The vulnerability is classified under CWE-20, indicating improper input validation. The CVSS v3.1 score of 9.8 reflects the vulnerability's critical nature, with an attack vector that is network-based (AV:N), requiring no privileges (PR:N) or user interaction (UI:N), and impacting confidentiality, integrity, and availability (C:H/I:H/A:H). Although no exploits have been reported in the wild yet, the ease of exploitation and the severity of impact make this a high-priority issue for developers and organizations using the 'req' package in their Go applications. The lack of authentication or user interaction requirements further increases the risk. The vulnerability affects any system or service that relies on the vulnerable versions of the 'req' package, potentially exposing sensitive data or disrupting service operations.

Potential Impact

The impact of CVE-2024-45258 is significant for organizations worldwide that develop or operate Go-based applications using the vulnerable 'req' package. Exploitation can lead to unauthorized transmission of HTTP requests, which may result in data leakage, unauthorized access to internal or external services, and potential denial of service. This can compromise the confidentiality, integrity, and availability of affected systems. Organizations that rely on automated HTTP requests for critical business processes, API integrations, or microservices communication are particularly at risk. The vulnerability could be exploited remotely without authentication or user interaction, increasing the attack surface and potential for widespread exploitation. Additionally, the unintended requests could be leveraged to perform further attacks such as SSRF (Server-Side Request Forgery), data exfiltration, or lateral movement within networks. The absence of known exploits in the wild currently provides a window for remediation, but the critical CVSS score indicates that immediate action is necessary to prevent future attacks.

Mitigation Recommendations

To mitigate CVE-2024-45258, organizations should immediately update the 'req' package to version 3.43.4 or later, where the vulnerability has been addressed. Developers should audit their codebases to identify any usage of the vulnerable 'req' package versions and replace them accordingly. Implement strict input validation and sanitization for all URLs processed by applications, especially those that interact with external or user-supplied data. Employ network-level controls such as egress filtering and web application firewalls (WAFs) to detect and block anomalous or unintended outbound HTTP requests. Conduct thorough security testing, including fuzzing and static analysis, to identify similar input validation issues in related components. Monitor application logs for unusual request patterns that may indicate exploitation attempts. Additionally, educate development teams on secure coding practices to avoid reliance on components with 'garbage in, garbage out' designs. Finally, maintain an up-to-date inventory of third-party dependencies to enable rapid response to newly disclosed vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2024-08-25T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6ceab7ef31ef0b56a34d

Added to database: 2/25/2026, 9:43:06 PM

Last enriched: 2/26/2026, 8:12:00 AM

Last updated: 2/26/2026, 11:07:49 AM

Views: 1

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats