CVE-2018-7959
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 · uneditedThere is a short key vulnerability in Huawei eSpace product. An unauthenticated, remote attacker launches man-in-the-middle attack to intercept and decrypt the call information when the user enables SRTP to make a call. Successful exploitation may cause sensitive information leak.
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 confidenceA short key vulnerability exists in Huawei eSpace product's SRTP (Secure Real-time Transport Protocol) implementation. An unauthenticated remote attacker positioned on the network can perform a man-in-the-middle attack to intercept and decrypt sensitive call content due to insufficiently strong cryptographic keys used for SRTP encryption.
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= v200r003c30CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/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.
-
Confirm product and firmware versionAccess the Huawei eSpace 7950 admin interface or check the system firmware version information. This is typically available via the device management console or by running 'display version' or 'display device' commands on the device CLI.Affected if The firmware version equals v200r003c30 specifically.
-
Identify if SRTP is enabledNavigate to the call settings or telephony configuration section in the eSpace administration panel. Alternatively, check the SRTP status via CLI commands such as 'display sip service' or 'display srtp configuration' if available.Affected if SRTP (Secure RTP) is actively enabled for call handling.
-
Inspect SRTP cryptographic configurationLocate the SRTP encryption parameters in the product's security or call settings. Look for fields related to SRTP key length, cipher suites, or encryption algorithms. Compare the configured key size against industry standards (SRTP typically uses AES-128 or AES-256).Affected if The configured SRTP key length is shorter than the recommended minimum (for example, keys weaker than 128-bit) or weak/short keys are being used.
-
Verify network exposure of SRTP serviceDetermine if the eSpace 7950 SRTP ports (typically UDP ports 5000-6000 range or as configured) are accessible from untrusted networks. Use network scanning or check firewall rules.Affected if The SRTP service is reachable from external or untrusted network segments without appropriate filtering.
You are affected if you are running Huawei eSpace 7950 firmware v200r003c30 with SRTP enabled and the SRTP implementation is using weak or short cryptographic keys accessible from a network where an attacker could perform man-in-the-middle positioning.
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 patch from Huawei when available. In the interim, consider using VPN tunnels for voice traffic or implementing network segmentation to reduce the man-in-the-middle attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7959 — 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-2018-7959 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