How severe is GHSA-p72p-rjr2-r439?

No CVSS score has been assigned to GHSA-p72p-rjr2-r439 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p72p-rjr2-r439?

GHSA-p72p-rjr2-r439 affects the following packages: terriajs-server (npm). Ecosystems affected: npm.

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

Update terriajs-server to 2.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p72p-rjr2-r439 is resolved across your whole dependency graph.

How do I detect GHSA-p72p-rjr2-r439 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for terriajs-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-p72p-rjr2-r439 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-p72p-rjr2-r439?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p72p-rjr2-r439 can be triaged on real exposure rather than presence alone.

Is GHSA-p72p-rjr2-r439 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p72p-rjr2-r439 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-p72p-rjr2-r439 published, and has it been updated?

GHSA-p72p-rjr2-r439 was published on May 29, 2019 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-p72p-rjr2-r439 — terriajs-server

Fix: TerriaJS/terriajs-server@3cbc484

GHSA-p72p-rjr2-r439 is a security vulnerability in terriajs-server. A fix is available for terriajs-server — see the affected versions and patch details below.

Server-Side Request Forgery in terriajs-server

Published

May 29, 2019

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

terriajs-servernpm

963downloads / week

Description

Versions of terriajs-serverprior 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`terriajs-server`	all versions	2.7.4`npm install terriajs-server@2.7.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for terriajs-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update terriajs-server to 2.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p72p-rjr2-r439 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p72p-rjr2-r439 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-p72p-rjr2-r439. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-p72p-rjr2-r439 in your dependencies?

O3 Security finds GHSA-p72p-rjr2-r439 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works