cve.bz

CVE-2023-36661 SSRF

7.5 highExploitEPSS 2.9%

High (7.5). EPSS 2.9% estimated probability of exploitation activity in the next 30 days.

On this page
Shibboleth XMLTooling before 3.2.4, as used in OpenSAML and Shibboleth Service Provider, allows SSRF via a crafted KeyInfo element. (This is fixed in, for example, Shibboleth Service Provider 3.4.1.3 on Windows.)

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
2.9% (unchanged from 2.9% a week ago; 2.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 87th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-04-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-36661 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-36661?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-36661?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-36661 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
shibboleth:xmltoolingbefore 3.2.4
debian:debian_linux11.0
debian:debian_linux12.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian10xmltooling3.0.4-1+deb10u2DLA-3464-1
Debian11xmltooling3.2.0-3+deb11u1DSA-5432-1
Debian12xmltooling3.2.3-1+deb12u1DEBIAN-CVE-2023-36661 DSA-5432-1
Debian13, 14xmltooling3.2.4-1DEBIAN-CVE-2023-36661
Ubuntu14.04:LTS, 18.04:LTS, 20.04:LTS and 2 morexmltoolingno fix listedUBUNTU-CVE-2023-36661
UbuntuPro:16.04:LTSxmltooling1.5.6-2ubuntu0.3+esm1UBUNTU-CVE-2023-36661 USN-6274-1
SUSEEnterprise Storage 7.1, Linux Enterprise High Performance Computing 15 SP3-ESPOS, Linux Enterprise High Performance Computing 15 SP3-LTSS and 7 morexmltooling3.1.0-150300.3.3.1SUSE-SU-2023:3089-1
SUSELinux Enterprise Server 12 SP5, Linux Enterprise Server for SAP Applications 12 SP5, Linux Enterprise Software Development Kit 12 SP5xmltooling1.5.6-3.13.1SUSE-SU-2023:2975-1
openSUSELeap 15.4xmltooling1.6.4-150000.3.10.1SUSE-SU-2023:2766-1
openSUSELeap 15.4, Leap 15.5xmltooling3.1.0-150300.3.3.1SUSE-SU-2023:3089-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Fuse 7XMLToolingNot affected
Red Hat JBoss Data Virtualization 6XMLToolingOut of support scope
Red Hat JBoss Enterprise Application Platform 6XMLToolingOut of support scope
Red Hat JBoss Enterprise Application Platform 7xmltoolingNot affected
Red Hat JBoss Enterprise Application Platform 8xmltoolingNot affected
Red Hat JBoss Fuse 6xmltoolingOut of support scope
Red Hat Single Sign-On 7xmltoolingNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-36661.

Public exploits

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON