GHSA-373W-RJ84-PV6X

GHSA-373W-RJ84-PV6X is a low-severity security vulnerability in SafeURL-Python (pip), affecting versions < 1.3. It is fixed in 1.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

SafeURL-Python's hostname blocklist does not block FQDNs

Description

If a hostname was blacklisted, it was possible to bypass the blacklist by requesting the FQDN of the host (e.g. adding . to the end).

Credit

https://github.com/Sim4n6

Impact

The main purpose of this library is to block requests to internal/private IPs and these cannot be bypassed using this finding. But if a library user had specifically set certain hostnames as blocked, then an attacker would be able to circumvent that block to cause SSRFs to request those hostnames.

Affected versions

SafeURL-Python (< 1.3)

Security releases

SafeURL-Python → 1.3 (pip)

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 environmentNew to Kodem? Get a demo →

Remediation advice

Fixed by https://github.com/IncludeSecurity/safeurl-python/pull/6

Frequently Asked Questions

  1. What is GHSA-373W-RJ84-PV6X? GHSA-373W-RJ84-PV6X is a low-severity security vulnerability in SafeURL-Python (pip), affecting versions < 1.3. It is fixed in 1.3.
  2. Which versions of SafeURL-Python are affected by GHSA-373W-RJ84-PV6X? SafeURL-Python (pip) versions < 1.3 is affected.
  3. Is there a fix for GHSA-373W-RJ84-PV6X? Yes. GHSA-373W-RJ84-PV6X is fixed in 1.3. Upgrade to this version or later.
  4. Is GHSA-373W-RJ84-PV6X exploitable, and should I be worried? Whether GHSA-373W-RJ84-PV6X 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
  5. What actually determines whether GHSA-373W-RJ84-PV6X 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.
  6. How do I fix GHSA-373W-RJ84-PV6X? Upgrade SafeURL-Python to 1.3 or later.

Other vulnerabilities in SafeURL-Python

Stop the waste.
Protect your environment with Kodem.