# CVE-2017-10900: Missing authorization in PTW-WMS1

> Remote attackers can bypass access restrictions to read or delete data on the PTW-WMS1 device disk.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rmcp-m77m-wmrc

## What is CVE-2017-10900?

CVE-2017-10900 is a critical missing authorization vulnerability in Princeton Ltd. PTW-WMS1, published on 1 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PTW-WMS1 firmware version 2.000.012 allows remote attackers to bypass access restrictions to obtain or delete data on the disk via unspecified vectors.

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

It affects 1 product.


Products: Princeton Ptw-Wms1 Firmware.

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

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

## Is CVE-2017-10900 being exploited?

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

## Other vulnerabilities in Princeton Ltd. PTW-WMS1

- [CVE-2017-10902](https://insights.sbomify.com/CVE-2017-10902/): Command injection in PTW-WMS1 (critical 9.8)
- [CVE-2017-10903](https://insights.sbomify.com/CVE-2017-10903/): Auth bypass in PTW-WMS1 (critical 9.8)
- [CVE-2017-10901](https://insights.sbomify.com/CVE-2017-10901/): Memory corruption in PTW-WMS1 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10900 is a critical missing authorization vulnerability in Princeton Ltd. PTW-WMS1, published on 1 Dec 2017. 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-10900 in the wild and no public exploit code.

Affected product: Princeton Ltd. PTW-WMS1. 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-10900/ (Markdown: https://insights.sbomify.com/CVE-2017-10900/index.md)
```

## Sources

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

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