Ip Phone 6871 With Multiplatform FirmwareOperating system · Cisco
CVE-2024-20357
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 XML service of Cisco IP Phone firmware could allow an unauthenticated, remote attacker to initiate phone calls on an affected device. This vulnerability exists because bounds-checking does not occur while parsing XML requests. An attacker could exploit this vulnerability by sending a crafted XML request to an affected device. A successful exploit could allow the attacker to initiate calls or play sounds on 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 confidenceThe vulnerability exists in the XML parsing service of Cisco IP Phone firmware where proper bounds-checking is not performed. An unauthenticated remote attacker can send a specially crafted XML request to the affected device, potentially causing a buffer overflow or similar memory corruption that allows initiating arbitrary phone calls or playing audio.
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 6871 With Multiplatform FirmwareOperating system
<= 12.0.4
Ip Phone 7811 With Multiplatform FirmwareOperating system
<= 12.0.4
Ip Phone 7821 With Multiplatform FirmwareOperating system
<= 12.0.4
Ip Phone 7832 With Multiplatform FirmwareOperating system
<= 12.0.4
Ip Phone 7841 With Multiplatform FirmwareOperating system
<= 12.0.4
Ip Phone 7861 With Multiplatform FirmwareOperating system
<= 12.0.4
Ip Phone 8811 With Multiplatform FirmwareOperating system
<= 12.0.4
Ip Phone 8832 With Multiplatform FirmwareOperating system
<= 12.0.4CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 modelCheck the physical device label or access the phone's web interface or admin menu to confirm the exact model number (6871, 7811, 7821, 7832, 7841, 7861, 8811, or 8832)Affected if The model is NOT one of these eight affected models - if your model is different, you are not affected by this CVE
-
Check the installed firmware versionAccess the phone's web interface (usually at the device's IP address), navigate to the Administration or Info section, and locate the firmware version field. Alternatively, press the Settings button on the phone and look for Firmware Version or Software Version under the phone's info menuAffected if The firmware version is 12.0.4 or lower, or if the version cannot be determined but is known to be the multiplatform firmware release prior to the fix
-
Verify network exposure of the deviceCheck the network configuration and firewall rules to determine if the phone is accessible from untrusted or external networks. The XML parsing service listens on the device and can receive requests from network sourcesAffected if The phone is reachable from untrusted networks (such as the internet or guest networks) without network segmentation or firewall filtering - this is required for an unauthenticated remote attacker to exploit the vulnerability
Your environment is affected if you have a Cisco IP Phone model 6871, 7811, 7821, 7832, 7841, 7861, 8811, or 8832 running multiplatform firmware version 12.0.4 or lower, and the device is accessible from untrusted network segments.
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 the vendor-supplied firmware update from Cisco to address this vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure of the phone infrastructure to untrusted networks.
Fix this in Ip Phone 6871 With Multiplatform Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20357 — 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-20357 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