dbcve.org
Magic R300 2100m FirmwareOperating system · H3c

CVE-2023-33640

HIGH · 7.2 CVSS v3.1 Published 2023-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
H3C Magic R300 version R300-2100MV100R004 was discovered to contain a stack overflow via the SetAPWifiorLedInfoById 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 confidence

Stack overflow vulnerability in H3C Magic R300 router R300-2100MV100R004 in the SetAPWifiorLedInfoById web interface handler at /goform/aspForm. Insufficient input validation allows overflowing a stack-based buffer, potentially enabling remote code execution.

MitigationUpdate router firmware to latest version if available, otherwise restrict access to the web management interface to trusted networks only.

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
Magic R300 2100m FirmwareOperating system
Affected:= r300-2100mv100r004

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the router web administration interface or check the device label/sticker to confirm the model is H3C Magic R300 2100m
    Affected if Device is not H3C Magic R300 2100m - not affected
  2. Check firmware version
    Log into the router web interface and navigate to System Settings or Status page to view the firmware version. Compare against r300-2100mv100r004
    Affected if Firmware version is exactly r300-2100mv100r004 - affected
  3. Verify web interface is enabled
    Attempt to access the router web management interface at the default gateway IP (commonly 192.168.1.1) on ports 80 or 443
    Affected if Web interface is accessible - vulnerable handler is exposed; if web interface is disabled/restricted to localhost only - lower risk
  4. Confirm vulnerable endpoint exists
    Check if the URL /goform/aspForm is reachable by submitting a request to the router web interface
    Affected if Endpoint responds - the SetAPWifiorLedInfoById handler is present and potentially exploitable

User is affected if the device is H3C Magic R300 2100m running firmware version r300-2100mv100r004 and the web management interface at /goform/aspForm is accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update router firmware to latest version if available, otherwise restrict access to the web management interface to trusted networks only.

Fix this in Magic R300 2100m Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-33640 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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