dbcve.org
Ip Phone 8800 Series FirmwareOperating system · Cisco

CVE-2016-1435

HIGH · 7.0 CVSS v3.0 Published 2016-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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
Cisco 8800 phones with software 11.0(1) do not properly enforce mounted-filesystem permissions, which allows local users to write to arbitrary files by leveraging shell access, aka Bug ID CSCuz03014.

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

The vulnerability exists in Cisco 8800 series IP phones running software version 11.0(1), where mounted filesystem permissions are not properly enforced. A local attacker with shell access can write to arbitrary files on the device by exploiting this permission bypass, potentially enabling privilege escalation or firmware manipulation.

MitigationRestrict shell access to authorized personnel only, and upgrade Cisco 8800 phones to a patched software version beyond 11.0(1) that properly enforces filesystem permissions.

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 8800 Series FirmwareOperating system
Affected:= 11.0\(1\)

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

CVSS:3.0/AV:L/AC:H/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 firmware version on the Cisco 8800 IP phone
    Access the phone's web interface or use the Cisco IP Phone Administrator Guide commands to retrieve the firmware version. On the device, you can typically check this via the Settings > Phone menu or by accessing the device's web UI at its IP address and viewing the Device Information page.
    Affected if The displayed firmware version is exactly 11.0(1)
  2. Verify if shell or SSH access is enabled on the device
    Check the device configuration for enabled services. In the phone's web interface, navigate to Security Settings or CTI Settings to see if SSH or shell access is permitted. Alternatively, attempt to connect to the device on port 22 (SSH) or port 23 (Telnet) from a trusted management station.
    Affected if Shell or SSH access is enabled and reachable on the device
  3. Confirm mounted filesystem write permissions from shell context
    If shell access is available, log in and inspect mounted filesystems using commands like 'mount' or 'df -h'. Test write access to system directories by creating a temporary test file in a location that should normally be restricted (e.g., /etc or /var).
    Affected if A local authenticated user with shell access can write to directories that should be read-only (such as /etc or /firmware)
  4. Check for unauthorized firmware modifications
    If shell access is available, compare checksums of firmware-related files against known-good values, or review system log files for unexpected modification timestamps on critical system files.
    Affected if Firmware or system files show signs of unauthorized modification or unexpected timestamps

You are affected if your Cisco 8800 series phone runs firmware version exactly 11.0(1) AND shell/SSH access is enabled on the device, allowing a local attacker to bypass filesystem permission controls.

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

Restrict shell access to authorized personnel only, and upgrade Cisco 8800 phones to a patched software version beyond 11.0(1) that properly enforces filesystem permissions.

Fix this in Ip Phone 8800 Series Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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