CVE-2011-4625 json
simpleSAMLphp incorrectly handles XML encryption
published 2019-11-06 7 y ago modified 2026-06-16 4 mo ago also GHSA-5fj7-f8x3-q2mc , EUVD-2022-1634
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
simplesamlphp before 1.6.3 (squeeze) and before 1.8.2 (sid) incorrectly handles XML encryption which could allow remote attackers to decrypt or forge messages.
Patch / fix
- packagist simplesamlphp/simplesamlphp 1.8.1
- simplesamlphp simplesamlphp 1.6.3, 1.8.2
- simplesamlphp Debian 14, Debian 12 1.8.1-1
debian advisories DEBIAN-CVE-2011-4625
Exploit prediction
0.74% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | simplesamlphp/simplesamlphp | <1.8.1 |
1.8.1 |
Affected products
- simplesamlphp simplesamlphp
Classification
- Weakness
-
- CWE-755 Improper Handling of Exceptional Conditions
References
-
security-tracker.debian.org
/tracker/CVE-2011-4625
web, third-party-advisory
-
mageni.net
/1.3.6.1.4.1.25623.1.0.70545
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2011-4625
advisory
-
github.com
/simplesamlphp/simplesamlphp
package
-
github.com
/simplesamlphp/simplesamlphp/blob/b3059c51a915910c6631fb2ee597c0fb6ad9162b/docs/simplesamlphp-changelog-1.x.md
web
-
secure1.securityspace.com
/smysecure/catid.html?in=DSA%202330-1
web
-
mageni.net
/vulnerability/debian-security-advisory-dsa-2330-1-simplesamlphp-70545
web
Sources
- CVE List CVE-2011-4625
- GitHub Advisory GHSA-5fj7-f8x3-q2mc
- NVD CVE-2011-4625
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.