CVE-2023-33641
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 AddMacList 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 confidenceA stack overflow vulnerability exists in the H3C Magic R300 router (version R300-2100MV100R004) in the AddMacList web interface at /goform/aspForm. The lack of input validation on the MAC address list parameter allows an attacker to overflow the stack buffer, potentially enabling remote code execution with elevated privileges on the device.
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 administrative interface or check via SNMP/telnet. Look for 'H3C Magic R300' or '2100m' in the device information page, typically found under Status or System Info.Affected if The device is an H3C Magic R300 2100m router.
-
Verify the firmware versionIn the router's web admin panel, navigate to System Settings or Status page to view the firmware version. Alternatively, check via telnet/SSH using 'cat /proc/version' or 'ver' command if available.Affected if The firmware version is exactly R300-2100MV100R004.
-
Confirm the web interface is accessibleAttempt to access the router's web interface on the typical ports 80 or 443. Verify that the login page or admin panel loads successfully.Affected if The router's administrative web interface is reachable on the network.
-
Check if the aspForm endpoint existsSend an HTTP GET or POST request to http://<router-ip>/goform/aspForm and observe the response. A valid endpoint will return a response rather than a 404 error.Affected if The /goform/aspForm endpoint is present and responds to requests.
-
Verify the AddMacList functionality is presentAccess the MAC filtering or wireless access control section in the router's web interface. Look for an option to add MAC addresses to a whitelist or blacklist.Affected if The router has a MAC address filtering feature that uses the AddMacList function.
You are affected if you have an H3C Magic R300 2100m router running firmware version R300-2100MV100R004 with its web interface accessible and the MAC filtering feature enabled.
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 update when available. Until then, restrict access to the router's administrative web interface to trusted networks only, or implement network segmentation to minimize exposure to unauthenticated attackers.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33641 — 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-33641 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