CVE-2016-6670
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 S7700, S9300, S9700, and S12700 devices with software before V200R008C00SPC500 use random numbers with insufficient entropy to generate self-signed certificates, which makes it easier for remote attackers to discover private keys by leveraging knowledge of a certificate.
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 confidenceHuawei S7700, S9300, S9700, and S12700 devices use a weak random number generator with insufficient entropy when creating self-signed certificates. This allows attackers who obtain the public certificate to more easily derive the corresponding private key, compromising the cryptographic protection the certificate was meant to provide.
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= v200r005c00= v200r003c00= v200r005c00= v200r003c00= v200r005c00= v200r003c00= v200r005c00CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 device model and firmware versionUse command 'display version' or check device management interface to confirm the exact model (S7700, S9300, S9700, or S12700) and firmware versionAffected if Device model is S7700, S9300, S9700, or S12700 AND firmware version is exactly v200r003c00 or v200r005c00 (or falls within those specific release lines)
-
Locate self-signed certificatesUse command 'display ssl policy' or check the device's SSL/pki configuration to list all certificates configured on the deviceAffected if Any self-signed certificates exist on the device (certificates created on the device itself rather than imported from a trusted CA)
-
Check certificate generation timestampUse 'display ssl policy' or 'display pki certificate' commands to view certificate details including validity start date and creation timestampAffected if Self-signed certificates were created while the device was running an affected firmware version (v200r003c00 or v200r005c00) - verify the certificate creation date falls within the period the affected firmware was in use
-
Review certificate key strengthUse 'display pki certificate detail' or export certificate and analyze with openssl (openssl x509 -in cert.pem -text) to check the key size and algorithmAffected if Certificate uses RSA key sizes smaller than 2048 bits or shows other signs of weak key generation (note: this is a secondary indicator as weak keys can also result from other causes)
The device is likely affected if it is an S7700, S9300, S9700, or S12700 running firmware v200r003c00 or v200r005c00 and has self-signed certificates that were generated while running that firmware.
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 dataReplace all self-signed certificates on affected devices with new certificates generated using a cryptographically secure random number generator with proper entropy sources. Ensure devices are updated to V200R008C00SPC500 or later which contains the fix.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6670 — 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-2016-6670 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