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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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 pinpoints whether GHSA-p72p-rjr2-r439 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-p72p-rjr2-r439

GHSA-p72p-rjr2-r439 is a security vulnerability in terriajs-server. O3 Security confirms whether GHSA-p72p-rjr2-r439 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Server-Side Request Forgery in terriajs-server

Published

May 29, 2019

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

terriajs-servernpm

1Kdownloads / 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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-p72p-rjr2-r439 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 detects GHSA-p72p-rjr2-r439 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works