# CVE-2013-2153: Security feature bypass in n/a

> Attackers can bypass XML digital signature verification to spoof arbitrary content by reusing signatures in crafted Reference elements.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-2153, GHSA-3rvj-2vfj-frq8

## What is CVE-2013-2153?

CVE-2013-2153 is a medium-severity vulnerability in n/a, published on 20 Aug 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The XML digital signature functionality (xsec/dsig/DSIGReference.cpp) in Apache Santuario XML Security for C++ (aka xml-security-c) before 1.7.1 allows context-dependent attackers to reuse signatures and spoof arbitrary content via crafted Reference elements in the Signature, aka "XML Signature Bypass issue."

Weakness: CWE-310

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

It affects 1 product.


Products: Apache Xml Security for C\+\+.

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

Upgrade to a fixed version.

## Is CVE-2013-2153 being exploited?

There is no known exploitation of CVE-2013-2153 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-2011-2516](https://insights.sbomify.com/CVE-2011-2516/): Integer overflow in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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