# CVE-2017-9383: Server-side request forgery in n/a

> Attackers can exploit a UPnP service to force the device to fetch arbitrary URLs, enabling Server-Side Request Forgery and potential internal network access.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2xg5-f76f-ff8q

## What is CVE-2017-9383?

CVE-2017-9383 is a critical server-side request forgery vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices. The device provides UPnP services that are available on port 3480 and can also be accessed via port 80 using the url "/port_3480". It seems that the UPnP services provide "wget" as one of the service actions for a normal user to connect the device to an external website. It retrieves the parameter "URL" from the query string and then passes it to an internal function that uses the curl module on the device to retrieve the contents of the website.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-9383?

It affects 2 products.


Products: Getvera Veraedge Firmware, Getvera Veralite Firmware.

## How do I fix CVE-2017-9383?

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

## Is CVE-2017-9383 being exploited?

There is no known exploitation of CVE-2017-9383 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-9385](https://insights.sbomify.com/CVE-2017-9385/): Path traversal in n/a (critical 9.8)
- [CVE-2017-9381](https://insights.sbomify.com/CVE-2017-9381/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-9384](https://insights.sbomify.com/CVE-2017-9384/): Command injection in n/a (high 8.8)
- [CVE-2017-9388](https://insights.sbomify.com/CVE-2017-9388/): Command injection in n/a (high 8.8)
- [CVE-2017-9389](https://insights.sbomify.com/CVE-2017-9389/): Auth bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9383 and fix it if it is affected.

What it is: CVE-2017-9383 is a critical server-side request forgery vulnerability in n/a, published on 17 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9383 in the wild and no public exploit code.

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-2017-9383/ (Markdown: https://insights.sbomify.com/CVE-2017-9383/index.md)
```

## Sources

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

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