dbcve.org
Ar120 S FirmwareOperating system · Huawei

CVE-2017-15343

HIGH · 7.5 CVSS v3.0 Published 2018-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Huawei 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 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 confidence

Integer overflow vulnerability in Huawei AR3200 V200R006C10-V200R008C30 where the software insufficiently validates certain fields in SCTP messages, allowing a remote unauthenticated attacker to send a crafted SCTP message causing system reboot.

MitigationApply Huawei firmware patches for the affected versions; as an interim control, consider blocking or restricting SCTP traffic at network boundaries if not required for legitimate business functions.

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
Ar120 S FirmwareOperating system
Affected:= v200r006c10= v200r007c00= v200r008c20= v200r008c30
Ar1200 FirmwareOperating system
Affected:= v200r007c01= v200r007c02
Ar3200 FirmwareOperating system
Affected:= v200r006c11= v200r008c00= v200r008c10

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

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

  1. Identify the Huawei AR device model
    Log into the device CLI and run 'display device' or 'display version' to confirm the hardware model (AR120, AR1200, or AR3200 series)
    Affected if Device is a Huawei AR120, AR1200, or AR3200 series router
  2. Check the installed firmware version
    Run 'display version' in the device CLI to view the current software version; compare it against the affected versions: AR120 = v200r006c10, v200r007c00, v200r008c20, v200r008c30; AR1200 = v200r007c01, v200r007c02; AR3200 = v200r006c11, v200r008c00, v200r008c10
    Affected if The displayed firmware version matches one of the listed affected versions exactly
  3. Verify if SCTP protocol is enabled
    Run 'display current-configuration | include sctp' or check the configuration for any SCTP-related settings; also run 'display ip sla' or check if SCTP is configured in any protocol settings
    Affected if SCTP protocol is enabled or configured on the device (the vulnerability only triggers when processing SCTP traffic)
  4. Check for SCTP listening endpoints
    Run 'display sctp status' or 'display sctp association' if available, to see active SCTP associations or listeners
    Affected if The device has active SCTP associations or is listening on SCTP ports (default SCTP port 38412 or custom)
  5. Review inbound SCTP traffic filtering
    Check ACLs, firewall policies, or interface configurations for any rules that permit or block SCTP traffic (port 38412); use 'display acl all' or inspect the packet filter configuration
    Affected if SCTP traffic from untrusted sources can reach the device (no network-level filtering blocks it)

The device is likely affected if it is a Huawei AR120/AR1200/AR3200 running one of the listed affected firmware versions AND SCTP protocol is enabled or configured, allowing unauthenticated SCTP traffic to reach the device.

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

Apply Huawei firmware patches for the affected versions; as an interim control, consider blocking or restricting SCTP traffic at network boundaries if not required for legitimate business functions.

Fix this in Ar120 S Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15343 — 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-2017-15343 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