CVE-2013-4632
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 · uneditedThe Huawei Access Router (AR) before V200R002SPC003 allows remote attackers to cause a denial of service (device reset) via a crafted field in a DHCP request, as demonstrated by a request from an IP phone.
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 confidenceHuawei Access Router (AR) versions prior to V200R002SPC003 contain a vulnerability in DHCP request processing. A remote attacker can send a crafted DHCP request with a malicious field, causing the router to reset, resulting in denial of service. The attack can be launched remotely, as demonstrated by DHCP requests from IP phones.
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<= v200r002c01spc200CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
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 modelCheck if the target device is a Huawei Access Router (AR series) by running 'display device' or 'display version' command in the router CLIAffected if Device is not a Huawei AR series router
-
Check the firmware versionRun 'display version' in the router CLI to view the current software version. Compare it against the affected range: any version <= v200r002c01spc200Affected if Firmware version is v200r002c01spc200 or earlier, or any V200R002SPCxxx version prior to V200R002SPC003
-
Verify DHCP is enabledRun 'display ip interface' or 'display dhcp server' to check if DHCP server or relay functionality is configured on the routerAffected if DHCP server, relay, or client features are actively enabled on the device
-
Check network exposure to DHCP requestsReview interface configurations using 'display current-configuration interface' to determine if interfaces are exposed to untrusted broadcast networks where malicious DHCP requests could be receivedAffected if Interfaces have DHCP listening enabled and are connected to untrusted or shared network segments (e.g., guest networks, unmanaged switch ports)
The environment is affected if it contains a Huawei AR router with firmware version v200r002c01spc200 or earlier that has DHCP functionality enabled and is exposed to potentially untrusted DHCP request sources.
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 dataUpdate Huawei AR router firmware to version V200R002SPC003 or later to patch the vulnerability. If immediate patching is not possible, consider network segmentation to limit DHCP request sources to trusted devices.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4632 — 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-2013-4632 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