spatie/url-signer is vulnerable to Incorrect Type Conversion or Cast
69
CVE Score
Medium
Incorrect Type Conversion or Cast
Before the fix, validate in spatie/url-signer passed the expires query parameter of any supplied URL straight into an integer-typed timestamp comparison, with no type or integer check and before verifying the signature. Anyone able to get an application to validate a crafted URL, typically an unauthenticated visitor clicking a signed link, could send expires[] and cause an uncaught TypeError (a 500 or denial of service); non-integer numerics like 1e10 were silently coerced. The fix requires expires and signature to be strings and validates expires as an integer with filter_var, so malformed values return false instead of crashing or coercing.
Upgrade the spatie/url-signer package to 2.1.4 or later.
You are affected if you are using a version that falls within the vulnerable range and pass request URLs, such as signed links from unauthenticated clients, to validate() without first checking the expires parameter type.
2.0.0 - 2.1.3
Fixed in 2.1.4spatie/url-signer is vulnerable to Incorrect Type Conversion or Cast in versions 2.0.0 - 2.1.3.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.