@node-saml/node-saml's validatePostRequestAsync does not include checkTimestampsValidityError
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.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | @node-saml/node-saml | < 4.0.5 | 4.0.5 |
Referencias
- https://github.com/node-saml/node-saml/security/advisories/GHSA-vx8m-6fhw-pccw
- https://nvd.nist.gov/vuln/detail/CVE-2023-40178
- https://github.com/node-saml/node-saml/commit/045e3b9c54211fdb95f96edf363679845b195cec
- https://github.com/node-saml/node-saml
- https://github.com/node-saml/node-saml/releases/tag/v4.0.5
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L- Debilidad (CWE)
CWE-347, CWE-613- Plataforma
- npm
- Paquete
@node-saml/node-saml- Publicada
- 21.08.2023
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-vx8m-6fhw-pccw - CC BY 4.0
Historial de vulnerabilidades: @node-saml/node-saml
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 4
- Primera → última
- 10.2022 07.2025
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 2
- Alta 1
- Media 1
Divulgaciones por año
- 2022: 1
- 2023: 1
- 2024: 0
- 2025: 2
- 2026: 0
-
@node-saml/node-saml's validatePostRequestAsync does not include checkTimestampsValidityError esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.