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

> Buffer overflow in Cisco DX650 allows arbitrary code execution via incorrect memory allocation.

- **Severity:** Medium 6.6 (`AV:L/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 2 Jul 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-8mgm-f953-x9j5

## What is CVE-2013-3399?

CVE-2013-3399 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jul 2013. 

### Official description

Buffer overflow in an unspecified Android API on the Cisco Desktop Collaboration Experience DX650 allows attackers to execute arbitrary code via vectors that leverage incorrect memory allocation, aka Bug IDs CSCuf93957, CSCug22352, and CSCug22462.

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

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

It affects 1 product.


Products: Cisco Desktop Collaboration Experience.

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

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

## Is CVE-2013-3399 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3399 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jul 2013. 
Exploitation: There is no known exploitation of CVE-2013-3399 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-3399/ (Markdown: https://insights.sbomify.com/CVE-2013-3399/index.md)
```

## Sources

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

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