---
title: "CVE-2024-47832: SSOReady has an XML Signature Bypass via differential XML parsing"
url: https://erroneo.us/security/cve/CVE-2024-47832/
description: "CVE-2024-47832 (github.com/ssoready/ssoready (Go)): ssoready is a single sign on provider implemented via docker. Affected versions are vulnerable to XML…"
type: vulnerability-record
section: "Security Digest"
date_published: 2024-10-09
date_modified: 2024-10-11
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2024-47832"
kev: false
cvss: 9.3
epss: 0.00401
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2024-47832: SSOReady has an XML Signature Bypass via differential XML parsing

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.4% , percentile 33: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 33% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes github.com/ssoready/ssoready (Go) < 0.0.0-20241009153838-7f92a0630439, fixed in 0.0.0-20241009153838-7f92a0630439 . Check your lockfile, including transitive dependencies.

## What it is

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.

## Affected packages

- Go `github.com/ssoready/ssoready` < 0.0.0-20241009153838-7f92a0630439 → fixed: 0.0.0-20241009153838-7f92a0630439

## Affected products (CVE record)

- ssoready ssoready: < 0.0.0-20241009153838-7f92a0630439

## Severity

- GitHub_M CVSS 4.0: 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`
- GitHub CVSS 4.0: 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`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.40% probability of exploitation activity in the next 30 days; percentile 33.

## Sources

- [GitHub Advisory GHSA-j2hr-q93x-gxvh](https://github.com/advisories/GHSA-j2hr-q93x-gxvh)
- [CVE.org record CVE-2024-47832](https://www.cve.org/CVERecord?id=CVE-2024-47832)
- [NVD entry CVE-2024-47832](https://nvd.nist.gov/vuln/detail/CVE-2024-47832)
- [github.com](https://github.com/ssoready/ssoready/security/advisories/GHSA-j2hr-q93x-gxvh)
- [github.com](https://github.com/ssoready/ssoready/commit/7f92a0630439972fcbefa8c7eafe8c144bd89915)
- [ssoready.com](https://ssoready.com/docs/self-hosting/self-hosting-sso-ready)
- [pkg.go.dev](https://pkg.go.dev/vuln/GO-2024-3185)

---
Source page: https://erroneo.us/security/cve/CVE-2024-47832/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt