Skip to content
Fencer Intel
critical 9.3

CVE-2013-2808 json

Heap-based buffer overflow in Xper in Philips Xper Information Management Physiomonitoring 5 components, Xper Information Management Vascul…

published 2013-10-05 13 y ago modified 2026-06-16 4 mo ago also EUVD-2013-2747

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.3%
EPSS 4.3% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

Heap-based buffer overflow in Xper in Philips Xper Information Management Physiomonitoring 5 components, Xper Information Management Vascular Monitoring 5 components, and Xper Information Management servers and workstations for Flex Cardio products before XperConnect 1.5.4.053 SP2 allows remote attackers to execute arbitrary code via a crafted HTTP request to the Connect broker on TCP port 6000.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-13-277-01 updated cvss 9.3

Philips Xper Buffer Overflow Vulnerability

  • Philips Xper Information Management (Flex Cardio product line) servers and workstations Philips Xper Information Management Physiomonitoring 5 system components Philips Xper Information Management Vascular Monitoring 5 system components
    affected: mitigation “Philips has released an update, XperConnect 1.5.4.053 SP2, that mitigates this vulnerability. Philips has tested the update and verified that it resolves the vulnerability”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

4.35% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel 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.