# CVE-2024-34580: Server-side request forgery in n/a

> An SSRF vulnerability in Apache XML Security for C++ allows attackers to exploit KeyInfo elements, though the project disputes this as a configuration issue.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2024
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-j4fv-r5w9-h675, UBUNTU-CVE-2024-34580

## What is CVE-2024-34580?

CVE-2024-34580 is a medium-severity server-side request forgery vulnerability in n/a, published on 26 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Apache XML Security for C++ through 2.0.4 implements the XML Signature Syntax and Processing (XMLDsig) specification without protection against an SSRF payload in a KeyInfo element. NOTE: the project disputes this CVE Record on the grounds that any vulnerabilities are the result of a failure to configure XML Security for C++ securely. Even when avoiding this particular issue, any use of this library would need considerable additional code and a deep understanding of the standards and protocols involved to arrive at a secure implementation for any particular use case. We recommend against continued direct use of this library.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-34580?


## How do I fix CVE-2024-34580?

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

## Is CVE-2024-34580 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34580 and fix it if it is affected.

What it is: CVE-2024-34580 is a medium-severity server-side request forgery vulnerability in n/a, published on 26 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34580 exists.

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-2024-34580/ (Markdown: https://insights.sbomify.com/CVE-2024-34580/index.md)
```

## Sources

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

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