CVE-2015-6017
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities in Forms/rpAuth_1 on ZyXEL P-660HW-T1 2 devices with ZyNOS firmware 3.40(AXH.0) allow remote attackers to inject arbitrary web script or HTML via the (1) LoginPassword or (2) hiddenPassword parameter.
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 confidenceMultiple reflected XSS vulnerabilities exist in the ZyXEL P-660HW-T1 v2 router's web authentication form (Forms/rpAuth_1). The LoginPassword and hiddenPassword parameters are not properly sanitized before being reflected in the HTML response, allowing remote attackers to inject arbitrary JavaScript or HTML via crafted URLs or form submissions.
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= 3.40\(axh.0\)CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 the device modelAccess the router's web administration interface or check the device label/marketing to confirm the exact model is ZyXEL P-660HW-T1 v2Affected if The device is NOT a ZyXEL P-660HW-T1 v2 router
-
Check the firmware versionLog into the router's web interface and navigate to Status or Maintenance > Firmware Version, or use the router's command-line interface if accessible, to determine the installed firmware versionAffected if The firmware version is 3.40(axh.0)
-
Confirm web management interface is enabledAttempt to access the router's web interface via HTTP (port 80) or HTTPS (port 443) from a client on the networkAffected if The web interface is accessible and responds to requests
-
Test for XSS in authentication formSubmit a crafted request to Forms/rpAuth_1 with a test payload in the LoginPassword or hiddenPassword parameters (such as <script>alert(1)</script>) and inspect the HTML response to see if the input is reflected without sanitizationAffected if The submitted payload is reflected unmodified in the response HTML
The environment is affected only if the device is specifically a ZyXEL P-660HW-T1 v2 router running firmware version 3.40(axh.0) with its web management interface accessible.
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 available ZyXEL firmware updates; if no update exists, implement network segmentation to isolate the device and consider replacing end-of-life hardware. Deploy WAF rules to filter malicious input on affected parameters as a compensating control.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6017 — 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-2015-6017 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