# CVE-2024-47832: XML Signature Bypass via differential XML parsing in ssoready

> Attackers can bypass XML signature verification in self-hosted SSOReady instances by exploiting differential XML parsing behavior.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2024
- **Updated:** 11 Oct 2024
- **Also known as:** GHSA-j2hr-q93x-gxvh, GO-2024-3185

## What is CVE-2024-47832?

CVE-2024-47832 is a critical vulnerability in ssoready, published on 9 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ssoready is a single sign on provider implemented via docker. Affected versions are vulnerable to XML signature bypass attacks. An attacker can carry out signature bypass if you have access to certain IDP-signed messages. The underlying mechanism exploits differential behavior between XML parsers. Users of https://ssoready.com, the public hosted instance of SSOReady, are unaffected. We advise folks who self-host SSOReady to upgrade to 7f92a06 or later. Do so by updating your SSOReady Docker images from sha-... to sha-7f92a06. There are no known workarounds for this vulnerability.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

3 open source packages ship an affected version, including github.com/ssoready/ssoready. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ssoready/ssoready` | Go | All versions | None |
| `github.com/ssoready/ssoready` | Go | All versions | 0.0.0-20241009153838-7f92a0630439 |
| `github.com/ssoready/ssoready` | Go | All versions | 0.0.0-20241009153838-7f92a0630439 |

Products: Ssoready Ssoready.

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

Upgrade github.com/ssoready/ssoready to 0.0.0-20241009153838-7f92a0630439 or later.

## Is CVE-2024-47832 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47832 is a critical vulnerability in ssoready, published on 9 Oct 2024. 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-47832 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ssoready/ssoready (Go): affected all versions; no fix listed
- github.com/ssoready/ssoready (Go): affected all versions; fixed in 0.0.0-20241009153838-7f92a0630439
- github.com/ssoready/ssoready (Go): affected all versions; fixed in 0.0.0-20241009153838-7f92a0630439

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

## Sources

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

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