CVE-2017-10900
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPTW-WMS1 firmware version 2.000.012 allows remote attackers to bypass access restrictions to obtain or delete data on the disk via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePTW-WMS1 firmware version 2.000.012 contains an authentication bypass vulnerability that allows remote attackers to circumvent access controls and perform unauthorized read or delete operations on disk data. The specific exploitation vector is not detailed in available documentation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.000.012CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PTW-WMS1 system in environmentLocate and inventory any Princeton PTW-WMS1 systems on the network by reviewing device listings, asset management records, or scanning for the product identifierAffected if PTW-WMS1 hardware or firmware is present in the environment
-
Check firmware versionAccess the system admin interface or firmware management console and verify the installed firmware version is 2.000.012Affected if Firmware version is exactly 2.000.012
-
Verify remote access exposureCheck network configuration to determine if the PTW-WMS1 management interface is exposed to untrusted networks or external IP addressesAffected if System management interface is reachable from untrusted networks
-
Audit disk data access logsReview system audit logs for any unauthorized read or delete operations on disk data, particularly from sources that should not have authentication credentialsAffected if Logs show disk read or delete operations from unauthenticated or unauthorized sources
-
Check for unauthorized authentication bypass indicatorsExamine authentication logs for successful accesses that bypassed normal credential verification or originated from unexpected sourcesAffected if Authentication logs contain entries indicating bypass of normal access controls
The environment is affected if a Princeton PTW-WMS1 system is running firmware version 2.000.012 and has its management interface network-accessible, enabling remote attackers to bypass authentication and manipulate disk data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware updates if available; if no patch exists, implement network segmentation to isolate the affected system and restrict external access as compensating controls until a fix is released.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10900 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-10900 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data