CVE-2017-11351
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 · uneditedAxesstel MU553S MU55XS-V1.14 devices have a default password of admin for the admin account.
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 confidenceThe Axesstel MU553S MU55XS-V1.14 wireless router ships with a hardcoded default credential for the administrative account using username 'admin' and password 'admin'. This default credential allows remote attackers to gain full administrative access to the device's management interface, enabling configuration changes, network monitoring, or further network compromise.
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= mu553s-v1.14CVSS 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 the device modelAccess the router's web management interface (typically at 192.168.1.1 or 192.168.0.1) and navigate to the Status or Device Information page to view the model number. Alternatively, check the physical device label or use network discovery tools like nmap to identify the device.Affected if The device model is Axesstel MU553S or Mu553s
-
Check the firmware versionIn the router's web interface, locate the firmware version under Status, Device Info, or System Settings. The affected version is mu553s-v1.14.Affected if The firmware version is exactly mu553s-v1.14
-
Verify credential statusAttempt to log in to the administrative web interface using the default credentials (username: admin, password: admin). If login succeeds with these credentials, the default password has not been changed.Affected if Login succeeds with admin/admin credentials, indicating the default password remains active
-
Check for remote management exposureDetermine if the router's web management interface is accessible from external networks (WAN). Use nmap or similar tool to scan the public IP assigned to the router for HTTP/HTTPS ports (80, 443, 8080, 8443).Affected if The administrative interface is accessible from the WAN side
You are affected if you have an Axesstel MU553S router running firmware version mu553s-v1.14 with the default credentials (admin/admin) still active, especially if remote management is enabled.
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 dataImmediately change the default admin password to a strong, unique password through the device's web management interface, and disable remote management access if external administration is not required.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11351 — 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-11351 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