Unified Ip Phone 7906Hardware / appliance · Cisco

CVE-2011-1603

MEDIUM · 6.6 CVSS v2.0 Published 2011-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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 Unified IP Phones 7900 devices (aka TNP phones) with software before 9.2.1 allow local users to gain privileges via unspecified vectors, aka Bug ID CSCtn65815.

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

Local privilege escalation vulnerability in Cisco Unified IP Phones 7900 series (TNP phones) running software versions prior to 9.2.1. An authenticated local user can exploit unspecified vectors to gain elevated privileges on the device, potentially accessing administrative functions.

MitigationUpgrade Cisco Unified IP Phone 7900 firmware to version 9.2.1 or later. In enterprise deployments, this is typically managed through Cisco CallManager/Unity by applying the appropriate device load and performing a firmware distribution to affected phones.

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 Phone 7906Hardware / appliance
Affected:all versions
Unified Ip Phone 7911gHardware / appliance
Affected:all versions
Unified Ip Phone 7931gHardware / appliance
Affected:all versions
Unified Ip Phone 7941gHardware / appliance
Affected:all versions
Unified Ip Phone 7941g GeHardware / appliance
Affected:all versions
Unified Ip Phone 7942gHardware / appliance
Affected:all versions
Unified Ip Phone 7945gHardware / appliance
Affected:all versions
Unified Ip Phone 7961gHardware / appliance
Affected:all versions

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
M
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:M/Au:S/C:C/I:C/A:C

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. Inventory Cisco Unified IP Phone 7900 series devices
    Review your network inventory or Cisco CallManager/Unity device list to identify if any of these models are deployed: 7906, 7911g, 7931g, 7941g, 7941g Ge, 7942g, 7945g, or 7961g
    Affected if Any of these phone models are present in the environment
  2. Check phone firmware version
    Access the phone's web interface (if enabled) or query via Cisco CallManager administration console to retrieve the current firmware load version. On the physical phone, press Settings > Model Information > firmware version
    Affected if Firmware version is prior to 9.2.1 (for example, 9.0, 8.x, or earlier)
  3. Verify local access availability
    Determine if the phone allows local console access, SSH, or telnet administration. Check device security settings in Cisco CallManager under Device > Device Settings > Phone Security Profile
    Affected if Local administrative access methods (console, SSH, or telnet) are enabled on the phone
  4. Check for unauthorized local accounts
    If local access is available, review the phone's local user accounts and privilege levels by accessing the device configuration or examining authentication logs
    Affected if Unexpected local accounts exist or privilege escalation has already occurred

If any Cisco Unified IP Phone 7900 series model is deployed with firmware versions prior to 9.2.1, the environment is affected by this privilege escalation vulnerability.

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

Upgrade Cisco Unified IP Phone 7900 firmware to version 9.2.1 or later. In enterprise deployments, this is typically managed through Cisco CallManager/Unity by applying the appropriate device load and performing a firmware distribution to affected phones.

Fix this in Unified Ip Phone 7906 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-2011-1603 — 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-2011-1603 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