# CVE-2013-2808: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted HTTP requests to the Connect broker in Philips Xper Information Management systems.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2pcp-wj44-rx86

## What is CVE-2013-2808?

CVE-2013-2808 is a critical memory corruption vulnerability in n/a, published on 5 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-2808?

It affects 4 products.


Products: Philips Xper Flex Cardio, Philips Xper Information Management Physiomonitoring 5, Philips Xper Information Management Vascular Monitoring 5, Philips Xperconnect.

## How do I fix CVE-2013-2808?

No fix has been published for CVE-2013-2808 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-2808 being exploited?

There is no known exploitation of CVE-2013-2808 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2808 and fix it if it is affected.

What it is: CVE-2013-2808 is a critical memory corruption vulnerability in n/a, published on 5 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2808 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-2808/ (Markdown: https://insights.sbomify.com/CVE-2013-2808/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2808
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2808
- OSV: https://osv.dev/vulnerability/CVE-2013-2808

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2808/
Summaries are generated and may contain mistakes; the official description above is the record.