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

> Remote attackers can cause a denial of service via a buffer overflow triggered by large RSA keys in the XML signature feature.

- **Severity:** Medium 5.0 (`AV:N/AC:L/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:** 11 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-2516, DSA-2277-1, GHSA-2jmv-v2x6-mmv8

## What is CVE-2011-2516?

CVE-2011-2516 is a medium-severity vulnerability in n/a, published on 11 Jul 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Off-by-one error in the XML signature feature in Apache XML Security for C++ 1.6.0, as used in Shibboleth before 2.4.3 and possibly other products, allows remote attackers to cause a denial of service (crash) via a signature using a large RSA key, which triggers a buffer overflow.

Weakness: CWE-189

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

It affects 2 products.


Products: Apache Xml Security for C\+\+, Shibboleth Shibboleth-Sp.

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

Upgrade to a fixed version.

## Is CVE-2011-2516 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2154](https://insights.sbomify.com/CVE-2013-2154/): Memory corruption in n/a (high 7.5)
- [CVE-2013-2156](https://insights.sbomify.com/CVE-2013-2156/): Memory corruption in n/a (high 7.5)
- [CVE-2013-2210](https://insights.sbomify.com/CVE-2013-2210/): Memory corruption in n/a (high 7.5)
- [CVE-2013-2155](https://insights.sbomify.com/CVE-2013-2155/): Security feature bypass in n/a (medium 5.8)
- [CVE-2013-2153](https://insights.sbomify.com/CVE-2013-2153/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2516 is a medium-severity vulnerability in n/a, published on 11 Jul 2011. 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-2011-2516 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-2011-2516/ (Markdown: https://insights.sbomify.com/CVE-2011-2516/index.md)
```

## Sources

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

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