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

> Remote attackers can cause a denial of service via a buffer overflow in the libsrtp library, affecting applications using this secure RTP implementation.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-2840-1, GHSA-p6g5-gwj7-cvr6, MGASA-2014-0465

## What is CVE-2013-2139?

CVE-2013-2139 is a low-severity memory corruption vulnerability in Fedoraproject Fedora, published on 16 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in srtp.c in libsrtp in srtp 1.4.5 and earlier allows remote attackers to cause a denial of service (crash) via vectors related to a length inconsistency in the crypto_policy_set_from_profile_for_rtp and srtp_protect functions.

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

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

It affects 3 products.


Products: Cisco Libsrtp, Fedoraproject Fedora, Opensuse Opensuse.

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

Upgrade to a fixed version.

## Is CVE-2013-2139 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2139 is a low-severity memory corruption vulnerability in Fedoraproject Fedora, published on 16 Jan 2014. 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-2139 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-2139/ (Markdown: https://insights.sbomify.com/CVE-2013-2139/index.md)
```

## Sources

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

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