CVE-2017-8174
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 USG6300 V100R001C30SPC300 and USG6600 with software of V100R001C30SPC500,V100R001C30SPC600,V100R001C30SPC700,V100R001C30SPC800 have a weak algorithm vulnerability. Attackers may exploit the weak algorithm vulnerability to crack the cipher text and cause confidential information leaks on the transmission links.
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 confidenceThe affected Huawei USG6300 and USG6600 firewall products use weak cryptographic algorithms in their encryption implementation. Attackers can exploit this vulnerability to crack encrypted data in transit, exposing confidential information being transmitted over protected links.
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= v100r001c30spc300= v100r001c30spc500= v100r001c30spc600= v100r001c30spc700= v100r001c30spc800CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Huawei firewall modelLog into the device management interface or check the physical device label to confirm the model is either USG6300 or USG6600Affected if The device model is not USG6300 or USG6600, then this CVE does not apply
-
Check the installed firmware versionAccess the device CLI or web management interface and retrieve the firmware version. This is typically shown in the system information or version display command outputAffected if The firmware version is v100r001c30spc300 for USG6300, or any of v100r001c30spc500, v100r001c30spc600, v100r001c30spc700, v100r001c30spc800 for USG6600, indicating a vulnerable version
-
Locate the encryption configuration settingsAccess the device configuration menus for SSL VPN, IPSec VPN, or general encryption settings. These are typically found under Security settings, VPN configuration, or System settings depending on the interfaceAffected if The device has SSL VPN, IPSec, or other encryption features configured and enabled
-
Inspect the cryptographic algorithms in useReview the cipher suites, encryption algorithms, and hash algorithms configured for protected links. Check for the presence of weak algorithms such as DES, 3DES, MD5, or SHA1Affected if Weak cryptographic algorithms (such as DES, 3DES, MD5, or SHA1) are enabled or configured for any encryption feature on the device
The device is affected if it is a USG6300 or USG6600 running one of the listed vulnerable firmware versions AND has encryption features enabled using weak cryptographic algorithms.
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 dataUpgrade to a patched software version provided by Huawei, or if no patch is available, reconfigure the device to use strong encryption ciphers (e.g., AES-256, SHA-256) and disable weak algorithms.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8174 — 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-8174 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