CVE-2023-33633
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 · uneditedH3C Magic R300 version R300-2100MV100R004 was discovered to contain a stack overflow via the UpdateWanParams interface at /goform/aspForm.
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 confidenceA stack overflow vulnerability exists in the H3C Magic R300 router (version R300-2100MV100R004) in the UpdateWanParams interface at /goform/aspForm. The lack of proper bounds checking on user-supplied input allows an attacker to overflow the stack buffer, potentially leading to arbitrary code execution or denial of service.
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= r300-2100mv100r004CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 modelAccess the router's web管理界面 (web management interface) and check the device information page, or check the device label/marketing packaging for the model number. Confirm it is an H3C Magic R300 series router.Affected if The device is not an H3C Magic R300 router.
-
Check firmware versionIn the router web interface, navigate to System Settings, Status, or Device Info page to find the firmware version. Look for a version string such as 'R300-2100MV100R004' or similar.Affected if The installed firmware version is R300-2100MV100R004 exactly.
-
Verify web management interface accessibilityAttempt to access http://[router-ip]/goform/aspForm from a browser. The vulnerability exists in the UpdateWanParams function at this endpoint. You may also check if port 80 or 443 is open on the router's WAN interface.Affected if The router's web interface on /goform/aspForm is reachable from untrusted networks (not just local LAN).
-
Check UpdateWanParams parameter handlingIf you have access to the router's administration, navigate to WAN settings (such as PPPoE, DHCP, or static IP configuration). The vulnerability occurs when the UpdateWanParams interface processes overly long input in fields such as username, password, or WAN IP settings.Affected if You can submit unusually long strings (more than typical field lengths) to WAN parameter fields without the router rejecting them for exceeding expected length.
You are affected if you have an H3C Magic R300 router running firmware version R300-2100MV100R004 and the router's web management interface at /goform/aspForm is accessible from your network.
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-supplied firmware updates when available. Until then, restrict access to the router's web management interface to trusted networks only, as exploitation requires network access to the /goform/aspForm endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33633 — 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-33633 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