CVE-2023-40178
mediumpriority · track · 21EPSS 0.005 · 42 %ileEUUSEPSS · scored 2026-10-27
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
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-vx8m-6fhw-pccw@node-saml/node-saml's validatePostRequestAsync does not include checkTimestampsValidityError2023-08-21ghsa · osvUS
### Summary 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. ### Details It was noticed that in the validatePostRequestAsync() flow in saml.js, the current timestamp is never checked. This could present a vulnerability where a user who has an XML LogoutRequest could validated it if the IssueInstance and the NotOnOrAfter are valid along with valid credentials (signature, certificate etc.). ### PoC I was able to validate a sample valid LogoutRequest XML multiple times through postman by sending it to my endpoint regardless if the current present time was past the NotOnOrAfter time. After some further testing, it seems that only the IssueInstance is checked against NotOnOrAfter. Not sure if this was the intended behaviour but I believe having a never expiring valid LogoutRequest could be dangerous. ### Impact 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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (10)
External citations — patches, advisories, analysis.
- https://cxsecurity.com/cveshow/CVE-2023-40178/cnnvd
- https://github.com/node-saml/node-saml/commit/045e3b9c54211fdb95f96edf363679845b195ceccnnvd
- https://github.com/node-saml/node-saml/releases/tag/v4.0.5cnnvd
- https://github.com/node-saml/node-saml/security/advisories/GHSA-vx8m-6fhw-pccwcnnvd
- https://github.com/node-saml/node-saml/commit/045e3b9c54211fdb95f96edf363679845b195cecenisa_euvd
- https://github.com/node-saml/node-saml/releases/tag/v4.0.5enisa_euvd
- https://github.com/node-saml/node-saml/security/advisories/GHSA-vx8m-6fhw-pccwenisa_euvd
- https://github.com/node-saml/node-saml/commit/045e3b9c54211fdb95f96edf363679845b195cecPatchnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan