CVE-2017-15344
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 · uneditedHuawei AR3200 with software V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30 has an integer overflow vulnerability. The software does not sufficiently validate certain field in SCTP messages, a remote unauthenticated attacker could send a crafted SCTP message to the device. Successful exploit could cause system reboot.
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 confidenceThe Huawei AR3200 contains an integer overflow vulnerability in its SCTP message handling. A remote unauthenticated attacker can send a specially crafted SCTP message containing insufficiently validated fields, triggering the overflow and causing a system reboot (denial of service).
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= v200r006c10= v200r007c00= v200r008c20= v200r008c30= v200r007c01= v200r007c02= v200r006c11= v200r008c00= v200r008c10CVSS 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 the device modelLocate the physical device or check the device inventory to confirm the model is one of: AR120 S, AR1200, or AR3200Affected if The device is not one of these three models, then it is not affected by this CVE
-
Check the firmware versionAccess the device management interface or use the appropriate command to display the firmware version, then compare it against the affected versions: AR120 S (v200r006c10, v200r007c00, v200r008c20, v200r008c30), AR1200 (v200r007c01, v200r007c02), AR3200 (v200r006c11, v200r008c00, v200r008c10)Affected if The installed firmware version matches exactly one of the listed affected versions, then the device is vulnerable
-
Verify if SCTP protocol is enabledCheck the device configuration for any SCTP-related settings or protocol enablement, as the vulnerability only triggers when SCTP is activeAffected if SCTP is not configured or is disabled on the device, then the vulnerability cannot be exploited even with a matching firmware version
-
Assess network exposure to SCTP trafficReview firewall rules and network access controls to determine whether SCTP traffic (port 3643 or the configured SCTP port) can reach the device from untrusted networksAffected if SCTP traffic from unauthenticated remote sources can reach the device, then an attacker could exploit the vulnerability
The device is affected only if it is an AR120 S, AR1200, or AR3200 model running one of the listed firmware versions AND SCTP is enabled AND the device is reachable via SCTP traffic from untrusted networks.
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 the vendor-supplied firmware patch when available. As an interim control, block or filter SCTP traffic at network boundaries to prevent unauthenticated remote attackers from reaching the vulnerable device.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15344 — 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-15344 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