CVE-2023-33628
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 DelvsList 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 · high confidenceStack overflow vulnerability in H3C Magic R300 router (R300-2100MV100R004) in the DelvsList web interface at /goform/aspForm. Allows remote attackers to execute arbitrary code via crafted input due to insufficient bounds checking.
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 admin panel or check the device label/marketing to confirm it is an H3C Magic R300 router. The model number typically appears on the device itself or in the web interface header.Affected if Device is not an H3C Magic R300 model, then it is not affected by this specific CVE.
-
Check firmware versionLog into the router web interface and navigate to System Settings or Status page to view the firmware version. Alternatively, check via CLI if telnet/ssh is enabled. The version should be displayed as something like R300-2100MV100R004.Affected if Firmware version is exactly r300-2100mv100r004, then the device is running the affected version.
-
Verify web interface accessibilityAttempt to reach the router web interface via HTTP/HTTPS on the default gateway IP address (typically 192.168.1.1 or 192.168.0.1). Confirm the interface loads successfully.Affected if The web interface is accessible, proceed to check the specific vulnerable endpoint.
-
Check vulnerable endpoint exposureSend an HTTP request to http://[router-ip]/goform/aspForm to confirm the endpoint is reachable. The DelvsList parameter is handled by this endpoint.Affected if The /goform/aspForm endpoint responds (even with an error), the vulnerable code path is present on the device.
-
Assess network exposureDetermine if the router web interface (port 80/443) is exposed to the internet or untrusted networks. Check NAT/firewall rules on upstream devices or ISP gateway.Affected if The router web interface is accessible from untrusted networks (WAN side), the vulnerability can be exploited remotely.
The environment is affected if it contains an H3C Magic R300 router running firmware version r300-2100mv100r004 with the /goform/aspForm web interface accessible to attackers.
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 update when available; if unavailable, disable or restrict access to the /goform/aspForm web interface via firewall rules or network segmentation.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33628 — 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-33628 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