CVE-2023-33627
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 UpdateSnat 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-based buffer overflow in the H3C Magic R300 router's UpdateSnat web interface (/goform/aspForm). The vulnerability allows remote attackers to overwrite stack memory by sending specially crafted requests to the SNAT configuration endpoint, potentially enabling remote code execution.
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 the device modelAccess the router's web administration interface or check the device label/marketing materials to confirm it is an H3C Magic R300 router. Alternatively, examine HTTP response headers or the login page for 'H3C' or 'Magic R300' branding.Affected if The device is not an H3C Magic R300 router, then it is not affected by this specific CVE.
-
Determine the firmware versionLog into the router web interface and navigate to the System Settings, Firmware Upgrade, or Status page to view the current firmware version. The exact path varies by router interface but typically shows a version string like 'r300-2100mv100r004'.Affected if The installed firmware version is exactly r300-2100mv100r004, then the device falls within the affected version range.
-
Verify web interface accessibilityAttempt to access the router's web interface over HTTP/HTTPS on the typical management ports (80 or 443). Check if the endpoint /goform/aspForm is reachable by sending a request to http://[router-ip]/goform/aspForm.Affected if The web interface and the /goform/aspForm endpoint are accessible from the network, then the attack surface exists for this vulnerability.
-
Confirm UpdateSnat functionality existsReview the router's web interface for SNAT (Source Network Address Translation) configuration options, typically found under Firewall, NAT, or Network Settings. The vulnerability exists in the UpdateSnat function that processes SNAT configuration submissions.Affected if SNAT configuration functionality is present and accessible through the web interface, the vulnerable code path can be triggered.
If the device is an H3C Magic R300 2100m router running firmware version r300-2100mv100r004 and the web interface is network-accessible, the device is affected by CVE-2023-33627.
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 if available; if no update exists, restrict administrative access to the web interface to trusted networks only using firewall rules or VPN, as the vulnerability is exploitable remotely without authentication based on CVSS vector.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33627 — 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-33627 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