# CVE-2021-25939: ArangoDB - Blind SSRF when Downloading Foxx Service from URL

> A highly-privileged attacker can exploit ArangoDB's Foxx service download feature to perform blind Server-Side Request Forgery against internal localhost services.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vw3j-xfjf-6rj3

## What is CVE-2021-25939?

CVE-2021-25939 is a low-severity server-side request forgery vulnerability in arangodb, published on 9 Feb 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In ArangoDB, versions v3.7.0 through v3.9.0-alpha.1 have a feature which allows downloading a Foxx service from a publicly available URL. This feature does not enforce proper filtering of requests performed internally, which can be abused by a highly-privileged attacker to perform blind SSRF and send internal requests to localhost.

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

## Which versions are affected by CVE-2021-25939?

It affects 1 product.


Products: Arangodb Arangodb.

## How do I fix CVE-2021-25939?

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

## Is CVE-2021-25939 being exploited?

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

## Other vulnerabilities in arangodb

- [CVE-2021-25940](https://insights.sbomify.com/CVE-2021-25940/): ArangoDB - Insufficient Session Expiration after Password Change (high 8.8)
- [CVE-2021-25938](https://insights.sbomify.com/CVE-2021-25938/): Cross-site scripting in ArangoDB (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25939 and fix it if it is affected.

What it is: CVE-2021-25939 is a low-severity server-side request forgery vulnerability in arangodb, published on 9 Feb 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25939 in the wild and no public exploit code.

Affected product: arangodb. 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-2021-25939/ (Markdown: https://insights.sbomify.com/CVE-2021-25939/index.md)
```

## Sources

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

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