CVE-2023-33636
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 ipqos_lanip_editlist 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 confidenceStack overflow vulnerability in H3C Magic R300 router firmware R300-2100MV100R004. The overflow occurs in the ipqos_lanip_editlist form handler at /goform/aspForm, allowing potential remote code execution via crafted input exceeding stack buffer boundaries.
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 modelCheck if the device is an H3C Magic R300 2100m router by accessing the device web interface or checking the device label/firmware identificationAffected if Device is not an H3C Magic R300 2100m router, then not affected by this specific CVE
-
Check installed firmware versionAccess the router administration interface and navigate to the status or system information page to view the firmware version, or use the command line to retrieve the firmware version stringAffected if Firmware version is not exactly R300-2100MV100R004, then not affected by this specific CVE (only this exact version is listed as affected)
-
Verify ipqos feature is enabledAccess the router web interface and check the QoS or IP QoS settings configuration page to determine if the ipqos feature is configured or enabledAffected if The ipqos feature is disabled or not configured, then the vulnerable ipqos_lanip_editlist form handler is not accessible and the device is not affected by this specific flaw
-
Confirm /goform/aspForm endpoint accessibilityAttempt to access the /goform/aspForm endpoint on the router (typically requires authentication) or check the router's web server configuration for this endpointAffected if The /goform/aspForm endpoint is accessible (even with authentication), the stack overflow vulnerability in the ipqos_lanip_editlist form handler is present in the affected firmware version
A user is affected if they have an H3C Magic R300 2100m router running exactly firmware version R300-2100MV100R004 with the ipqos feature enabled and the /goform/aspForm endpoint 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 vendor firmware patch if available; otherwise, restrict administrative access to the device management interface through network segmentation or firewall rules to prevent unauthenticated attackers from reaching the /goform/aspForm endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33636 — 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-33636 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