# CVE-2019-8982: Server-side request forgery in n/a

> Attackers can exploit improper URL handling in WaveMaker Studio to read local files and perform server-side request forgery.

- **Severity:** Critical 9.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Feb 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xq3x-7w9j-26jf

## What is CVE-2019-8982?

CVE-2019-8982 is a critical server-side request forgery vulnerability in n/a, published on 21 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

com/wavemaker/studio/StudioService.java in WaveMaker Studio 6.6 mishandles the studioService.download?method=getContent&inUrl= value, leading to disclosure of local files and SSRF.

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

## Which versions are affected by CVE-2019-8982?

It affects 1 product.


Products: Wavemaker Wavemarker Studio.

## How do I fix CVE-2019-8982?

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

## Is CVE-2019-8982 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-8982 exists.

Public exploit code:

- Wavemaker Studio 6.6 - Server-Side Request Forgery (exploitdb)
- Wavemaker Studio 6.6 - Local File Inclusion/Server-Side Request Forgery (nuclei): http/cves/2019/CVE-2019-8982.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8982 and fix it if it is affected.

What it is: CVE-2019-8982 is a critical server-side request forgery vulnerability in n/a, published on 21 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-8982 exists.

Affected product: n/a. 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-2019-8982/ (Markdown: https://insights.sbomify.com/CVE-2019-8982/index.md)
```

## Sources

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

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