onelogin/php-saml Improper signature validation on LogoutRequest/LogoutResponse.

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

In order to verify Signatures on Logoutrequests and LogoutResponses we use the verifySignature of the class XMLSecurityKey from the xmlseclibs library. That method end up calling opensslverify() depending on the signature algorithm used. The opensslverify() function returns 1 when the signature was successfully verified, 0 if it failed to verify with the given key, and -1 in case an error occurs. PHP allows translating numerical values to boolean implicitly, with the following correspondences: - 0 equals false. - Non-zero equals true. This means that an implicit conversion to boolean of the values returned by opensslverify() will convert an error state, signaled by the value -1, to a successful verification of the signature (represented by the boolean true). The LogoutRequest/LogoutResponse signature validator was performing an implicit conversion to boolean of the values returned by the verify() method, which subsequently will return the same output as opensslverify() under most…

Published by the source

17 May 2024, 23:06 UTC

Last modified by the source

17 May 2024, 23:06 UTC

Source last checked

26 Oct 2026, 14:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9wrw-p9rm-r782

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-9wrw-p9rm-r782

Advisory: onelogin/php-saml Improper signature validation on LogoutRequest/LogoutResponse.
IDs: GHSA-9wrw-p9rm-r782
Record: https://patchnext.com/advisories/ghsa-9wrw-p9rm-r782 (revision 1, source checked 26 Oct 2026, 14:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: onelogin/php-saml 2.10.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist onelogin/php-saml: affected < 2.10.4; fixed in 2.10.4

## Suggested inspection (read-only)
- Packagist onelogin/php-saml: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on onelogin/php-saml.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9wrw-p9rm-r782 (GitHub-reviewed advisory GHSA-9wrw-p9rm-r782 lists affected ranges: Packagist onelogin/php-saml >=0 <2.10.4)

Commands are suggestions: review each one before running it.