Vulnerabilities/

Incorrect Authorization in serverless-offline

Severity:
High

Description

Serverless Offline 8.0.0 returns a 403 HTTP status code for a route that has a trailing / character, which might cause a developer to implement incorrect access control, because the actual behavior within the Amazon AWS environment is a 200 HTTP status code (i.e., possibly greater than expected permissions).

Recommendation

No fix is available yet. Followings are affected versions:

References

Related Issues

Tags:
npm
serverless-offline
Anything's wrong? Let us know Last updated on September 05, 2023

This issue is available in SmartScanner Professional

See Pricing