# CVE-2024-4227: gSOAP: Vulnerable to specially crafted unencrypted SDC messages

> An unauthenticated remote attacker can cause a denial of service via high CPU load in gSOAP when parsing XML with duplicate ID attributes under specific configurations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jan 2025
- **Updated:** 15 Jan 2025
- **Also known as:** DEBIAN-CVE-2024-4227, GHSA-v23x-2mww-cc32, OESA-2026-1189, UBUNTU-CVE-2024-4227

## What is CVE-2024-4227?

CVE-2024-4227 is a high-severity denial of service vulnerability in Genivia gSOAP, published on 15 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Genivia gSOAP with a specific configuration an unauthenticated remote attacker can generate a high CPU load when forcing to parse an XML having duplicate ID attributes which can lead to a DoS.

Weakness: CWE-834 (Excessive Iteration)

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


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

Apply the vendor's patch.

## Is CVE-2024-4227 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4227 is a high-severity denial of service vulnerability in Genivia gSOAP, published on 15 Jan 2025. 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-2024-4227 in the wild and no public exploit code.

Affected product: Genivia gSOAP. 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-4227/ (Markdown: https://insights.sbomify.com/CVE-2024-4227/index.md)
```

## Sources

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

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