Server-Side Request Forgery in terriajs-server
Priority LOW 38CWE-918Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix Fixed terriajs-server (npm): 2.7.4
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | terriajs-server (npm) | before 2.7.4 | 2.7.4 | Patch available | GHSA-p72p-rjr2-r439 |
- terriajs-server (npm) Vendor— Affected before 2.7.4 Fixed in 2.7.4 Patch available GHSA-p72p-rjr2-r439
Remediation
- Fix · GHSA-p72p-rjr2-r439 terriajs-server (npm) Fixed in 2.7.4 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-p72p-rjr2-r439
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences