CVE-2023-40178
The lack of checking of current timestamp allows a LogoutRequest XML to be reused multiple times even when the current time is past the NotOnOrAfter.
Does this matter?
Lower severity and a low EPSS score (0.49%). Track it; it rarely justifies an emergency change on its own.
Description
Node-SAML is a SAML library not dependent on any frameworks that runs in Node. The lack of checking of current timestamp allows a LogoutRequest XML to be reused multiple times even when the current time is past the NotOnOrAfter. This could impact the user where they would be logged out from an expired LogoutRequest. In bigger contexts, if LogoutRequests are sent out in mass to different SPs, this could impact many users on a large scale. This issue was patched in version 4.0.5.
- CVSS 3.1
- 5.3 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- EPSS
- 0.49% probability · 41th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-347, CWE-613
- Affected
- node saml project/node saml
- Source
- security-advisories@github.com
References
- https://github.com/node-saml/node-saml/commit/045e3b9c54211fdb95f96edf363679845b195cecPatch
- https://github.com/node-saml/node-saml/releases/tag/v4.0.5Release Notes
- https://github.com/node-saml/node-saml/security/advisories/GHSA-vx8m-6fhw-pccwVendor Advisory
- https://github.com/node-saml/node-saml/commit/045e3b9c54211fdb95f96edf363679845b195cecPatch
- https://github.com/node-saml/node-saml/releases/tag/v4.0.5Release Notes
- https://github.com/node-saml/node-saml/security/advisories/GHSA-vx8m-6fhw-pccwVendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.