Control ID IDSecure 4.7.26.0 and prior uses a hardcoded...
Critical severity
Unreviewed
Published
Aug 3, 2023
to the GitHub Advisory Database
•
Updated Apr 4, 2024
Description
Published by the National Vulnerability Database
Aug 3, 2023
Published to the GitHub Advisory Database
Aug 3, 2023
Last updated
Apr 4, 2024
Control ID IDSecure 4.7.26.0 and prior uses a hardcoded cryptographic key in order to sign and verify JWT session tokens, allowing attackers to sign arbitrary session tokens and bypass authentication.
References