CVE-2017-17312
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 · uneditedSome Huawei Firewall products USG2205BSR V300R001C10SPC600; USG2220BSR V300R001C00; USG5120BSR V300R001C00; USG5150BSR V300R001C00 have a DoS vulnerability in the IPSEC IKEv1 implementations of Huawei Firewall products. Due to improper handling of the malformed messages, an attacker may sent crafted packets to the affected device to exploit these vulnerabilities. Successful exploit the vulnerability could lead to device deny of service.
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 confidenceThis is a denial of service vulnerability in the IPSEC IKEv1 implementations of specific Huawei USG firewall models. The flaw allows remote attackers to send specially crafted malformed IKEv1 packets to trigger improper handling, causing the affected device to become unavailable.
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= v300r001c10spc600= v300r001c00= v300r001c00= v300r001c00CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Huawei USG modelAccess the device management interface or use 'display device' command to confirm the exact model (Usg2205bsr, Usg2220bsr, Usg5120bsr, or Usg5150bsr)Affected if Model is one of Usg2205bsr, Usg2220bsr, Usg5120bsr, or Usg5150bsr
-
Check installed firmware versionUse 'display version' or check device management interface to retrieve the current firmware versionAffected if Version matches v300r001c10spc600 (for Usg2205bsr) or v300r001c00 (for Usg2220bsr, Usg5120bsr, or Usg5150bsr)
-
Verify IPSEC IKEv1 is configuredUse 'display ike sa' or 'display ipsec sa' commands to check for active IPSEC security associations; check IKE configuration with 'display ike proposal' and review IKE version settingsAffected if IKEv1 is enabled or configured on any IPSEC tunnel
-
Check network exposure of IKE portsReview firewall rules and network accessibility of UDP ports 500 and 4500 (IKEv1 ports) from untrusted networksAffected if Device IKE ports are reachable from untrusted or internet-facing networks
If the device model and firmware version exactly match the affected versions listed AND IKEv1 is configured AND the device is exposed to untrusted IKE traffic, then the environment is vulnerable to this CVE.
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 Huawei vendor patches for the specific affected versions. If no patch is available, consider disabling IKEv1 and using IKEv2 only, or implement network-level filtering to restrict IKE traffic to trusted sources.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17312 — 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-2017-17312 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