CVE-2024-20445
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 UI of Cisco Desk Phone 9800 Series, Cisco IP Phone 7800 and 8800 Series, and Cisco Video Phone 8875 could allow an unauthenticated, remote attacker to access sensitive information on an affected device. This vulnerability is due to improper storage of sensitive information within the web UI of Session Initiation Protocol (SIP)-based phone loads. An attacker could exploit this vulnerability by browsing to the IP address of a device that has Web Access enabled. A successful exploit could allow the attacker to access sensitive information, including incoming and outgoing call records. Note: Web Access is disabled by default.
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 confidenceThe vulnerability stems from improper storage of sensitive information (including call records) within the web UI of SIP-based phone firmware. An unauthenticated remote attacker can access this data by browsing to the IP address of any affected Cisco phone that has Web Access enabled, without requiring authentication.
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= 3.1\(1\)= 3.1\(1\)= 3.1\(1\)= 3.1\(1\)< 14.3\(1\)< 14.3\(1\)< 14.3\(1\)< 14.3\(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 phone modelAccess the phone's web interface or check the device label/UI to determine the exact model number (e.g., Cisco IP Phone 7811, Cisco Desk Phone 9861, etc.)Affected if Model is one of: 9841, 9851, 9861, 9871, 7832, 8831, 8832, or 7811
-
Check firmware versionNavigate to the phone's web UI (if accessible) or access the device administration page to view the firmware version. Alternatively, check via the phone's status menu or CDP/LLDP neighbors on the connected switch.Affected if Firmware version is 3.1(1) for 9841/9851/9861/9871 models, or below 14.3(1) for 7832/8831/8832/7811 models
-
Verify Web Access statusAccess the phone's web interface or administration settings to check whether Web Access / HTTP Web Server is enabled. This is typically found under Network Settings, Administration, or Security settings on the device.Affected if Web Access is ENABLED on the device (vulnerability only applies when web access is turned on; it is disabled by default)
Device is affected if it matches an affected model, runs a firmware version within the specified ranges, AND has Web Access enabled, allowing unauthenticated access to stored call records via the web UI.
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.
dbcve · scoped14.3
Ensure Web Access remains disabled on all affected devices (it is disabled by default). If web access is required, apply vendor firmware updates when available or restrict web UI access to trusted networks via ACLs.
Firmware version 14.3(1) or later for IP Phone 7800/8800 series; Firmware version > 3.1(1) for Desk Phone 9800 series
- 1. Identify all affected Cisco Desk Phone 9800 Series, Cisco IP Phone 7800/8800 Series, and Cisco Video Phone 8875 devices on the network
- 2. Access the Cisco Software Download page (software.cisco.com) and download the latest firmware version for your specific phone model
- 3. Upgrade each affected device to firmware version 14.3(1) or later for IP Phone 7800/8800 series (including 7811, 7832, 8831, 8832)
- 4. For Desk Phone 9800 series (9841, 9851, 9861, 9871), upgrade to firmware version higher than 3.1(1) as specified in the Cisco security advisory
- 5. After upgrading, verify that Web Access remains disabled (it is disabled by default) or disable it if not needed: navigate to the phone's web UI > Security > Web Access and ensure it is set to Disabled
- 6. Verify the fix by attempting to access the web UI without credentials and confirming sensitive information is no longer exposed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20445 — 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-2024-20445 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