# CVE-2017-12575: Missing authorization in n/a

> Unauthenticated attackers can access sensitive router configuration data via exposed web APIs on NEC Aterm WG2600HP2 devices.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jgf4-v7wj-j4rg

## What is CVE-2017-12575?

CVE-2017-12575 is a high-severity missing authorization vulnerability in n/a, published on 24 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on the NEC Aterm WG2600HP2 1.0.2. The router has a set of web service APIs for access to and setup of the configuration. Some APIs don't require authentication. An attacker could exploit this vulnerability by sending a crafted HTTP request to retrieve DHCP clients, firmware version, and network status (ex.: curl -X http://[IP]/aterm_httpif.cgi/negotiate -d "REQ_ID=SUPPORT_IF_GET").

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Aterm Wg2600hp2 Firmware.

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

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

## Is CVE-2017-12575 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-20621](https://insights.sbomify.com/CVE-2021-20621/): Cross-site request forgery in Aterm WG2600HP and Aterm WG2600HP2 (high 8.8)
- [CVE-2021-20622](https://insights.sbomify.com/CVE-2021-20622/): Cross-site scripting in Aterm WG2600HP and Aterm WG2600HP2 (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12575 is a high-severity missing authorization vulnerability in n/a, published on 24 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12575 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-12575/ (Markdown: https://insights.sbomify.com/CVE-2017-12575/index.md)
```

## Sources

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

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