# CVE-2023-25557: Server-Side Request Forgery in DataHub

> Attackers can exploit a proxy flaw in DataHub to reroute requests to arbitrary hosts, potentially accessing internal services or sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-5w2h-q83m-65xg

## What is CVE-2023-25557?

CVE-2023-25557 is a high-severity server-side request forgery vulnerability in datahub-project datahub, published on 10 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2023-25557?

It affects 1 product.


Products: Datahub Datahub.

## How do I fix CVE-2023-25557?

No fix has been published for CVE-2023-25557 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-25557 being exploited?

There is no known exploitation of CVE-2023-25557 in the wild and no public exploit code.

## Other vulnerabilities in datahub-project datahub

- [CVE-2022-39366](https://insights.sbomify.com/CVE-2022-39366/): DataHub missing JWT signature check (critical 9.9)
- [CVE-2023-25559](https://insights.sbomify.com/CVE-2023-25559/): System account impersonation in DataHub (high 8.2)
- [CVE-2023-25560](https://insights.sbomify.com/CVE-2023-25560/): JSON Injection in DataHub (high 8.2)
- [CVE-2026-25644](https://insights.sbomify.com/CVE-2026-25644/): DataHub's LDAP Ingestion Source vulnerable to MITM attack through TLS downgrade (high 7.5)
- [CVE-2023-25562](https://insights.sbomify.com/CVE-2023-25562/): Failure to Invalidate Session on Logout in DataHub (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25557 and fix it if it is affected.

What it is: CVE-2023-25557 is a high-severity server-side request forgery vulnerability in datahub-project datahub, published on 10 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-25557 in the wild and no public exploit code.

Affected product: datahub-project datahub. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-25557/ (Markdown: https://insights.sbomify.com/CVE-2023-25557/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-25557
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-25557
- OSV: https://osv.dev/vulnerability/CVE-2023-25557

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-25557/
Summaries are generated and may contain mistakes; the official description above is the record.