Missing AuthenticationWeakness · CWE-306

CVE-2024-13173

HIGH · 7.5 CVSS v3.1 Published 2025-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The health module has insufficient restrictions on loading URLs, which may lead to some information leakage.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The health module contains insufficient restrictions on URL loading, allowing arbitrary URLs to be requested. This could enable an attacker to induce the application to make requests to attacker-controlled endpoints, potentially leaking sensitive information such as internal service details, credentials, or network topology.

MitigationImplement strict URL validation and allowlisting for the health module's URL loading functionality to restrict requests to trusted endpoints only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify health module with URL loading capability
    Locate any health check, monitoring, or status module in your application that has the ability to fetch or load URLs. This may be named 'health', 'healthcheck', 'status', 'monitoring', or similar. Search your codebase and configuration for functions that make HTTP requests as part of health status checking.
    Affected if Your application has a health module that can load URLs from external or internal sources
  2. Check if URL loading is enabled in health module configuration
    Review the health module's configuration files and settings to determine whether URL loading or remote resource fetching is enabled. Look for flags like 'enable_url_load', 'allow_remote_fetch', 'load_external_urls', or similar settings.
    Affected if URL loading or remote fetching is explicitly enabled in the health module configuration
  3. Inspect URL validation implementation
    Examine the health module source code or documentation to determine how URLs are validated before being requested. Check if there is an allowlist of permitted domains or if any URL can be specified.
    Affected if No URL validation, allowlisting, or domain restriction is implemented in the health module
  4. Test for arbitrary URL request capability
    If you have access to the health module interface, provide a test URL (such as a non-existent internal endpoint like http://internal-test.local or an external site) and observe whether the health module attempts to fetch it.
    Affected if The health module can be induced to make requests to arbitrary URLs, including internal network endpoints or attacker-controlled domains
  5. Review access logs for health module outbound requests
    Examine your application logs, proxy logs, or network traffic logs for outbound requests originating from the health module to unexpected or internal destinations that were not explicitly configured.
    Affected if Logs show the health module making requests to URLs that were not intentionally configured or are internal infrastructure

Your environment is affected if the health module has URL loading enabled without proper validation or allowlisting controls, allowing arbitrary URL requests to be made.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation and allowlisting for the health module's URL loading functionality to restrict requests to trusted endpoints only.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13173 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13173 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data