CVE-2017-9630
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 · uneditedAn Improper Authentication issue was discovered in PDQ Manufacturing LaserWash G5 and G5 S Series all versions, LaserWash M5, all versions, LaserWash 360 and 360 Plus, all versions, LaserWash AutoXpress and AutoExpress Plus, all versions, LaserJet, all versions, ProTouch Tandem, all versions, ProTouch ICON, all versions, and ProTouch AutoGloss, all versions. The web server does not properly verify that provided authentication information is correct.
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 · high confidencePDQ Manufacturing LaserWash and ProTouch series car wash control systems contain a web server that improperly verifies authentication credentials, allowing unauthenticated attackers to access the web interface. The vulnerability affects all versions of multiple product lines including LaserWash G5, M5, 360 series, and ProTouch ICON, among others.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Low
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 PDQ LaserWash or ProTouch devices on the networkInventory your network for PDQ Manufacturing car wash control systems. Check device labels, DHCP logs, or network scans for LaserWash G5, M5, 360, ProTouch ICON, or similar PDQ control panels.Affected if Any LaserWash G5, G5 S, M5, 360, 360 Plus, Autoxpress, Autoxpress Plus, Laserjet, or ProTouch ICON control system is present on the network.
-
Locate the web interface serviceScan the IP addresses of identified PDQ devices for open HTTP ports (typically port 80 or 443). Use a network scanner like nmap: nmap -p 80,443 <target_ip>Affected if The web interface is listening on HTTP (port 80) or HTTPS (port 443) on any PDQ device IP address.
-
Test unauthenticated web interface accessOpen a web browser and navigate to http://<device_ip> or https://<device_ip> without providing any username or password. Observe whether the car wash control dashboard or configuration page loads.Affected if The web control panel loads or displays any car wash interface without requiring login credentials.
-
Verify authentication is not enforcedAttempt to access protected pages or administrative functions within the web interface without logging in. Check if any operations or settings are accessible without a login prompt.Affected if Any administrative functions, status pages, or control features are accessible without first entering valid credentials.
If a PDQ LaserWash or ProTouch device has its web interface accessible on the network and it loads or allows operations without requiring authentication credentials, the environment is affected by CVE-2017-9630.
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 dataOrganizations should restrict network access to these industrial control system web interfaces, implement proper credential verification, and contact PDQ Manufacturing for firmware updates that address the authentication weakness.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9630 — 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-9630 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