Unified Ip Phones 9971 FirmwareOperating system · Cisco

CVE-2015-0604

MEDIUM · 5.0 CVSS v2.0 Published 2015-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The web framework on Cisco Unified IP 9900 phones with firmware 9.4(.1) and earlier allows remote attackers to upload files to arbitrary locations on a phone's filesystem via crafted HTTP requests, aka Bug ID CSCup90424.

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

Arbitrary file upload vulnerability in the web framework of Cisco Unified IP 9900 phones with firmware 9.4(1) and earlier. Remote attackers can upload files to arbitrary locations on the phone's filesystem via crafted HTTP requests, potentially enabling remote code execution.

MitigationUpdate Cisco Unified IP 9900 phones to firmware newer than 9.4(1). If immediate patching is not feasible, restrict network access to the phone web interfaces and implement network segmentation to reduce attack surface.

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
Unified Ip Phones 9971 FirmwareOperating system
Affected:= 9.4\(.1\)
Unified Ip Phones 9951 FirmwareOperating system
Affected:= 9.4\(.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
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/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 phone model
    Access the phone's web interface or check the physical device label to determine if it is a Cisco Unified IP Phone 9951 or 9971. Alternatively, use network scanning or Cisco device discovery to identify the model.
    Affected if The model is a Cisco Unified IP Phone 9951 or 9971.
  2. Check the firmware version
    Access the phone's admin web interface and navigate to the firmware information page, or use the phone's menu (Settings > Device Information > Firmware Version) to determine the installed firmware version.
    Affected if The firmware version is 9.4(1) or earlier.
  3. Verify the web framework is enabled
    Attempt to access the phone's HTTP web interface by browsing to the phone's IP address. Check if port 80/443 is listening on the device using a port scanner or by checking the phone's network settings.
    Affected if The web interface is accessible and responding to HTTP requests.
  4. Assess network exposure
    Determine if the phone's web interface is reachable from untrusted networks by reviewing firewall rules, network segmentation, and access control lists. Scan the network to confirm the phone's IP is exposed to potentially malicious remote actors.
    Affected if The phone's web interface is accessible from networks outside the trusted administrative VLAN.

You are affected if you have Cisco Unified IP Phones 9951 or 9971 running firmware version 9.4(1) or earlier, with the web interface 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

Update Cisco Unified IP 9900 phones to firmware newer than 9.4(1). If immediate patching is not feasible, restrict network access to the phone web interfaces and implement network segmentation to reduce attack surface.

Fix this in Unified Ip Phones 9971 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

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