# GHSA-p72p-rjr2-r439: Server-Side Request Forgery in terriajs-server

> Attackers can exploit SSRF in terriajs-server to access private internal resources via whitelisted proxies or DNS manipulation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 May 2019

## What is GHSA-p72p-rjr2-r439?

GHSA-p72p-rjr2-r439 is a server-side request forgery vulnerability in terriajs-server, published on 29 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `terriajs-server`prior to 2.7.4 are vulnerable to Server-Side Request Forgery (SSRF). If an attacker has access to a server whitelisted by the terriajs-server proxy or if the attacker is able to modify the DNS records of a domain whitelisted by the terriajs-server proxy, the attacker can use the terriajs-server proxy to access any HTTP-accessible resources that are accessible to the server, including private resources in the hosting environment.

## Recommendation

Upgrade to version 2.7.4 or later.

## Which versions are affected by GHSA-p72p-rjr2-r439?

2 open source packages ship an affected version, including terriajs-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `terriajs-server` | npm | All versions | 2.7.4 |
| `terriajs-server` | npm | All versions | 2.7.4 |

## How do I fix GHSA-p72p-rjr2-r439?

Upgrade terriajs-server to 2.7.4 or later.

## Is GHSA-p72p-rjr2-r439 being exploited?

There is no known exploitation of GHSA-p72p-rjr2-r439 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-p72p-rjr2-r439 and fix it if it is affected.

What it is: GHSA-p72p-rjr2-r439 is a server-side request forgery vulnerability in terriajs-server, published on 29 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-p72p-rjr2-r439 in the wild and no public exploit code.

Affected packages and fixed versions:
- terriajs-server (npm): affected all versions; fixed in 2.7.4
- terriajs-server (npm): affected all versions; fixed in 2.7.4

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/GHSA-p72p-rjr2-r439/ (Markdown: https://insights.sbomify.com/GHSA-p72p-rjr2-r439/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-p72p-rjr2-r439

---
From sbomify Insights: https://insights.sbomify.com/GHSA-p72p-rjr2-r439/
Summaries are generated and may contain mistakes; the official description above is the record.