Ip Phone Multiplatform FirmwareOperating system · Cisco

CVE-2018-0341

HIGH · 8.8 CVSS v3.0 Published 2018-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability in the web-based UI of Cisco IP Phone 6800, 7800, and 8800 Series with Multiplatform Firmware before 11.2(1) could allow an authenticated, remote attacker to perform a command injection and execute commands with the privileges of the web server. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by including arbitrary shell commands in a specific user input field. Cisco Bug IDs: CSCvi51426.

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

Command injection vulnerability in the web-based management UI of Cisco IP Phone 6800, 7800, and 8800 Series with Multiplatform Firmware. An authenticated attacker can inject arbitrary shell commands through insufficiently validated user input fields, executing with web server privileges. The vulnerability exists in versions prior to 11.2(1).

MitigationApply Cisco firmware update 11.2(1) or later to affected phone series. Restrict web UI access to trusted administrators only until the update is applied.

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
Ip Phone Multiplatform FirmwareOperating system
Affected:= 11.1\(2\)

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 phone model
    Access the phone's web-based management interface by navigating to the IP address of the device in a browser, or check the physical phone for the model number (6800, 7800, or 8800 series)
    Affected if The device is a Cisco IP Phone 6800, 7800, or 8800 Series with Multiplatform Firmware
  2. Determine the installed firmware version
    Locate the firmware version information in the web-based management UI, typically under Administration > System > Software Version or a similar status page, or access it via the phone's administration menu
    Affected if The firmware version is 11.1(2) or any version prior to 11.2(1)
  3. Verify web-based management UI is enabled
    Check the phone's web-based management UI settings, usually found under Administration > Web Server or similar security/network configuration sections
    Affected if The web-based management UI is enabled and accessible over the network
  4. Confirm authentication to web UI is possible
    Attempt to access the login page of the web-based management interface using the device IP address, or verify that administrator credentials are configured
    Affected if The web UI is accessible and accepts authentication credentials, allowing an attacker to log in and inject commands through user input fields

The environment is affected if the device is a Cisco IP Phone 6800, 7800, or 8800 Series running Multiplatform Firmware version 11.1(2) or any version prior to 11.2(1), with the web-based management UI enabled and accessible.

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 Cisco firmware update 11.2(1) or later to affected phone series. Restrict web UI access to trusted administrators only until the update is applied.

Fix this in Ip Phone Multiplatform Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-0341 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