What is CVE-2024-45258?

CVE-2024-45258 is a medium-severity improper input validation vulnerability in github.com/imroc/req/v3 (go), affecting versions < 3.43.4. It is fixed in 3.43.4. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2024-45258?

CVE-2024-45258 has a CVSS score of 7.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2024-45258?

github.com/imroc/req/v3 (go) versions < 3.43.4; github.com/imroc/req (go) versions < 3.43.4; github.com/imroc/req/v2 (go) versions < 3.43.4.

Is there a fix for CVE-2024-45258?

Yes. CVE-2024-45258 is fixed in 3.43.4. Upgrade to this version or later.

Is CVE-2024-45258 exploitable, and should I be worried?

Whether CVE-2024-45258 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-45258 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-45258 in github.com/imroc/req/v3

Q: How severe is CVE-2024-45258?

CVE-2024-45258 has a CVSS score of 7.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2024-45258?

github.com/imroc/req/v3 (go) versions < 3.43.4; github.com/imroc/req (go) versions < 3.43.4; github.com/imroc/req/v2 (go) versions < 3.43.4.

Q: Is there a fix for CVE-2024-45258?

Yes. CVE-2024-45258 is fixed in 3.43.4. Upgrade to this version or later.

Q: Is CVE-2024-45258 exploitable, and should I be worried?

Whether CVE-2024-45258 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-45258 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-45258?

Upgrade: github.com/imroc/req/v3 to 3.43.4 or later, github.com/imroc/req to 3.43.4 or later, github.com/imroc/req/v2 to 3.43.4 or later.

Summary

req may send an unintended request when a malformed URL is provided

The req library is a widely used HTTP library in Go. However, it does not handle malformed URLs effectively. As a result, after parsing a malformed URL, the library may send HTTP requests to unexpected destinations, potentially leading to security vulnerabilities or unintended behavior in applications relying on this library for handling HTTP requests.

Despite developers potentially utilizing the net/url library to parse malformed URLs and implement blocklists to prevent HTTP requests to listed URLs, inconsistencies exist between how the net/url and req libraries parse URLs. These discrepancies can lead to the failure of defensive strategies, resulting in potential security threats such as Server-Side Request Forgery (SSRF) and Remote Code Execution (RCE).

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2024-45258 has a CVSS score of 7.2 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.43.4); upgrading removes the vulnerable code path.

Affected versions

github.com/imroc/req/v3 (< 3.43.4) github.com/imroc/req (< 3.43.4) github.com/imroc/req/v2 (< 3.43.4)

Security releases

github.com/imroc/req/v3 → 3.43.4 (go) github.com/imroc/req → 3.43.4 (go) github.com/imroc/req/v2 → 3.43.4 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

github.com/imroc/req/v3 to 3.43.4 or later; github.com/imroc/req to 3.43.4 or later; github.com/imroc/req/v2 to 3.43.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-45258? CVE-2024-45258 is a medium-severity improper input validation vulnerability in github.com/imroc/req/v3 (go), affecting versions < 3.43.4. It is fixed in 3.43.4. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2024-45258? CVE-2024-45258 has a CVSS score of 7.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2024-45258?
- github.com/imroc/req/v3 (go) (versions < 3.43.4)
- github.com/imroc/req (go) (versions < 3.43.4)
- github.com/imroc/req/v2 (go) (versions < 3.43.4)
Is there a fix for CVE-2024-45258? Yes. CVE-2024-45258 is fixed in 3.43.4. Upgrade to this version or later.
Is CVE-2024-45258 exploitable, and should I be worried? Whether CVE-2024-45258 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-45258 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-45258?
- Upgrade github.com/imroc/req/v3 to 3.43.4 or later
- Upgrade github.com/imroc/req to 3.43.4 or later
- Upgrade github.com/imroc/req/v2 to 3.43.4 or later