dbcve.org
Espace 7950 FirmwareOperating system · Huawei

CVE-2018-7960

HIGH · 7.4 CVSS v3.0 Published 2018-11-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/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
There is a SRTP icon display vulnerability in Huawei eSpace product. An unauthenticated, remote attacker launches man-in-the-middle attack to intercept the packets in non-secure transmission mode. Successful exploitation may intercept and tamper with the call information, eventually 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 confidence

This is an SRTP (Secure Real-time Transport Protocol) icon display vulnerability in Huawei eSpace unified communications product. The vulnerability allows an unauthenticated remote attacker performing a man-in-the-middle attack to intercept and tamper with call information when the system operates in non-secure transmission mode. The issue likely involves the UI failing to properly indicate or enforce secure call status, enabling attackers to exploit the lack of encryption.

MitigationEnable SRTP (Secure RTP) encryption for all calls and ensure the system is configured to reject or warn about non-secure transmission. Implement network-level protections against MITM attacks such as mutual TLS authentication and certificate pinning.

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
Espace 7950 FirmwareOperating system
Affected:= v200r003c30

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checks

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

  1. Identify the product model
    Check the system information or product label to confirm the device is Huawei eSpace 7950
    Affected if The product is not Huawei eSpace 7950
  2. Check the firmware version
    Access the device management interface or use the command line to retrieve the firmware version (typically via 'display version' or through the web UI system info page)
    Affected if The firmware version is exactly v200r003c30
  3. Verify SRTP configuration status
    Check the call settings or VoIP/ telephony configuration menu for SRTP (Secure RTP) status - typically found under Call Settings, Telephony Settings, or Security Settings in the web management interface
    Affected if SRTP is disabled or set to optional/disabled in the call configuration
  4. Check call security indicator behavior
    Observe the call UI during an active call - verify whether the secure call indicator (lock icon or similar) correctly displays when SRTP is enabled, and whether it is missing or incorrect when SRTP is disabled
    Affected if The UI fails to display a non-secure indicator when calls are placed without SRTP encryption
  5. Verify non-secure transmission mode is allowed
    Check the system or call settings for options related to non-secure transmission, fallback to RTP, or allowing unencrypted calls
    Affected if The system is configured to permit non-secure transmission mode or has no enforcement of SRTP

You are affected if you have a Huawei eSpace 7950 device running firmware v200r003c30 with SRTP disabled or with settings that permit non-secure transmission mode, where the call UI does not properly indicate non-secure call status.

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

Enable SRTP (Secure RTP) encryption for all calls and ensure the system is configured to reject or warn about non-secure transmission. Implement network-level protections against MITM attacks such as mutual TLS authentication and certificate pinning.

Fix this in Espace 7950 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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