# CVE-2011-2702: Integer overflow in n/a

> An integer signedness error in Glibc's SSSE3 optimized memcpy allows attackers to execute arbitrary code via a negative length parameter.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 27 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r955-5974-3x3p

## What is CVE-2011-2702?

CVE-2011-2702 is a medium-severity vulnerability in Gnu Glibc, published on 27 Oct 2014. 

### Official description

Integer signedness error in Glibc before 2.13 and eglibc before 2.13, when using Supplemental Streaming SIMD Extensions 3 (SSSE3) optimization, allows context-dependent attackers to execute arbitrary code via a negative length parameter to (1) memcpy-ssse3-rep.S, (2) memcpy-ssse3.S, or (3) memset-sse2.S in sysdeps/i386/i686/multiarch/, which triggers an out-of-bounds read, as demonstrated using the memcpy function.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2011-2702?

It affects 2 products.


Products: Gnu Eglibc, Gnu Glibc.

## How do I fix CVE-2011-2702?

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

## Is CVE-2011-2702 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-2702 exists.

Public exploit code:

- eGlibc - Signedness Code Execution (exploitdb)

## Other vulnerabilities in Gnu Glibc

- [CVE-2013-4788](https://insights.sbomify.com/CVE-2013-4788/): Memory corruption in n/a (medium 5.1)
- [CVE-2011-1071](https://insights.sbomify.com/CVE-2011-1071/): Denial of service in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2702 and fix it if it is affected.

What it is: CVE-2011-2702 is a medium-severity vulnerability in Gnu Glibc, published on 27 Oct 2014. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-2702 exists.

Affected product: Gnu Glibc. 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-2011-2702/ (Markdown: https://insights.sbomify.com/CVE-2011-2702/index.md)
```

## Sources

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

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