Unified Ip Phone 6901 FirmwareOperating system · Cisco
CVE-2020-3360
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 · uneditedA vulnerability in the Web Access feature of Cisco IP Phones Series 7800 and Series 8800 could allow an unauthenticated, remote attacker to view sensitive information on an affected device. The vulnerability is due to improper access controls on the web-based management interface of an affected device. An attacker could exploit this vulnerability by sending malicious requests to the device, which could allow the attacker to bypass access restrictions. A successful attack could allow the attacker to view sensitive information, including device call logs that contain names, usernames, and phone numbers of users of the device.
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 confidenceImproper access controls in the Web Access feature of Cisco IP Phones Series 7800 and 8800 allow unauthenticated remote attackers to bypass authentication and view sensitive device information including call logs containing user names, usernames, and phone numbers.
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 6901 FirmwareOperating system
<= 12.8\(1\)
Unified Ip Phone 6961 FirmwareOperating system
<= 12.8\(1\)
Unified Ip Phone 6945 FirmwareOperating system
<= 12.8\(1\)
Unified Ip Phone 6941 FirmwareOperating system
<= 12.8\(1\)
Unified Ip Phone 6921 FirmwareOperating system
<= 12.8\(1\)
Unified Ip Phone 6911 FirmwareOperating system
<= 12.8\(1\)
Unified Ip Phone 7832 FirmwareOperating system
<= 12.8\(1\)
Unified Ip Phone 7861 FirmwareOperating system
<= 12.8\(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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the phone modelAccess the phone's web interface and navigate to the Device Information page, or check the physical device label, or query the device via SNMP or CDP/LLDP to identify the exact model number (e.g., Cisco Unified IP Phone 6941, 6961, 7800 series, 8800 series).Affected if The model is one of: Cisco Unified IP Phone 6901, 6911, 6921, 6941, 6945, 6961, 7832, or 7861.
-
Check the installed firmware versionIn the phone's web interface, go to Device Information or Administration page to view the firmware version. Alternatively, press the Settings button on the phone and navigate to Model Information to see the Software Version.Affected if The firmware version is 12.8(1) or any earlier version.
-
Verify if Web Access feature is enabledLog into the phone's web interface as an administrator and navigate to the Web Access or HTTP Server configuration section. Check whether the built-in web server is enabled or disabled.Affected if Web Access (HTTP/HTTPS server) is currently enabled on the device.
-
Confirm network accessibility of the web interfaceAttempt to reach the phone's web interface by entering its IP address in a browser (http://<phone_ip>). If the interface is accessible without authentication, the vulnerability is directly exploitable.Affected if The web management interface is reachable from an untrusted network and displays device information or a login prompt without requiring credentials.
You are affected if you have a Cisco Unified IP Phone model 6901, 6911, 6921, 6941, 6945, 6961, 7832, or 7861 running firmware version 12.8(1) or earlier, with Web Access enabled and accessible from your network.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Cisco firmware updates for affected phone series when available; until then, restrict network access to the web management interface via VLAN segmentation or firewall rules to limit exposure to untrusted networks.
Fix this in Unified Ip Phone 6901 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2020-3360 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-3360 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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