CVE-2023-3703
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 · uneditedProscend Advice ICR Series routers FW version 1.76 - CWE-1392: Use of Default Credentials
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 confidenceThe Proscend Advice ICR Series routers running firmware version 1.76 use default credentials (CWE-1392), allowing remote attackers to gain unauthorized administrative access to the device by using well-known or factory-set usernames and passwords.
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= 1.76= 1.76= 1.76= 1.76= 1.76= 1.76= 1.76= 1.76CVSS 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.1/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 device model and firmware versionAccess the router web interface or CLI and navigate to the status or system information page to retrieve the exact model name and firmware version number.Affected if The firmware version shown is 1.76 AND the model matches one of: M357 5g, M357 Ai, M350 5g, M350 W5g, M350 6, M350 W6, M331, or M330 W.
-
Verify default credentials are activeAttempt to log into the router admin interface using the well-known factory default username and password pair (such as admin/admin or admin/password). Check the product documentation or known default credential lists for the specific default pair.Affected if Login succeeds with the factory default credentials, indicating they have not been changed from the original setting.
-
Check remote management accessibilityDetermine if the router admin interface is accessible from the WAN/internet by testing connectivity to port 80 or 443 on the public IP address, or by reviewing the firewall/NAT settings in the router configuration.Affected if The router admin web interface is reachable from external networks without VPN or ACL restrictions.
The device is affected if it is a Proscend M357 or M350 or M331 or M330 W model running firmware version 1.76 AND the default credentials have not been changed AND the management interface is accessible (locally or remotely).
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 all default credentials to strong, unique passwords, disable remote management interfaces if not required, and update to the latest firmware version once available. Restrict network access to management interfaces via ACLs or VPN.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3703 — 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-2023-3703 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