Skip to content
Fencer Vulns
medium 5.9

CVE-2024-20357 json

A vulnerability in the XML service of Cisco IP Phone firmware could allow an unauthenticated, remote attacker to initiate phone calls on an…

published 2024-05-01 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-18072

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits
0
none known

Summary

A 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.

Patch / fix

  • cisco video_phone_8875_firmware 2.3.1.0101

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected products

  • Cisco Cisco IP Phones with Multiplatform Firmware
  • Cisco Cisco PhoneOS
  • cisco ip_phone_6871_with_multiplatform_firmware
  • cisco ip_phone_6821_with_multiplatform_firmware
  • cisco ip_phone_6851_with_multiplatform_firmware
  • cisco ip_phone_7821_with_multiplatform_firmware
  • cisco ip_phone_6861_with_multiplatform_firmware
  • cisco ip_phone_6825_with_multiplatform_firmware
  • cisco ip_phone_6841_with_multiplatform_firmware
  • cisco ip_phone_7811_with_multiplatform_firmware
  • cisco ip_phone_7841_with_multiplatform_firmware
  • cisco ip_phone_7861_with_multiplatform_firmware
  • cisco ip_phone_8800_series_with_multiplatform_firmware
  • cisco video_phone_8875_firmware

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.