dbcve.org
DatahubApplication

CVE-2023-25557

CRITICAL · 9.1 CVSS v3.1 Published 2023-02-11
Fix available
A fix is available. Upgrade to 0.8.45 or later.
See remediation →
100/100
Remediation priority · Urgent
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
DataHub is an open-source metadata platform. The DataHub frontend acts as a proxy able to forward any REST or GraphQL requests to the backend. The goal of this proxy is to perform authentication if needed and forward HTTP requests to the DataHub Metadata Store (GMS). It has been discovered that the proxy does not adequately construct the URL when forwarding data to GMS, allowing external users to reroute requests from the DataHub Frontend to any arbitrary hosts. As a result attackers may be able to reroute a request from originating from the frontend proxy to any other server and return the result. This vulnerability was discovered and reported by the GitHub Security lab and is tracked as GHSL-2022-076.

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 · high confidence

The DataHub frontend proxy improperly constructs URLs when forwarding REST/GraphQL requests to the backend GMS service, allowing attackers to specify arbitrary external hosts as the forwarding destination. This Server-Side Request Forgery (SSRF) vulnerability enables attackers to have the frontend proxy forward requests to any server and return the response.

MitigationImplement strict URL validation in the frontend proxy to whitelist only legitimate backend GMS hostnames/IPs and reject any requests attempting to route to external or arbitrary hosts.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DatahubApplication
Affected:< 0.8.45

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Check your DataHub version
    Locate the installed DataHub version in your deployment (typically via Docker image tag, helm chart version, or package manager). Compare it to the affected range: versions prior to 0.8.45 are vulnerable.
    Affected if The installed version is lower than 0.8.45
  2. Verify the frontend proxy component is in use
    Confirm that your DataHub deployment includes the frontend proxy component (datahub-frontend or equivalent) which handles REST and GraphQL request forwarding to the GMS backend service.
    Affected if The frontend proxy component is deployed and accessible to users or attackers
  3. Identify GMS backend configuration
    Locate the configuration that defines the backend GMS service URL that the frontend proxy forwards requests to. This is typically found in application configuration files or environment variables controlling the proxy behavior.
    Affected if The frontend proxy is configured to forward requests to a GMS backend service
  4. Inspect URL validation controls
    Review any URL validation or allowlist logic present in the frontend proxy configuration. Check whether the proxy validates or restricts the forwarding destination to only trusted GMS hostnames or IPs.
    Affected if No strict URL validation exists, or the proxy allows arbitrary hostnames in the forwarding destination

You are affected if your DataHub version is below 0.8.45 and the frontend proxy component is exposed, as attackers could then direct it to forward requests to arbitrary external hosts.

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.

dbcve · scoped
Upgrade available Upgrade to 0.8.45 or later
Fixed in 0.8.45
Interim mitigation

Implement strict URL validation in the frontend proxy to whitelist only legitimate backend GMS hostnames/IPs and reject any requests attempting to route to external or arbitrary hosts.

Recommended fix High confidence

0.8.45

  1. Upgrade DataHub to version 0.8.45 or later to remediate the SSRF vulnerability in the frontend proxy

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Datahub Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2023-25557 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