Unauthorized API access via mismatched trailing-slash routing
Published Aug 10, 2021 · Updated Aug 4, 2024
Incorrect authorization emulation in Serverless Offline 8.0.0 allows remote attackers to access a trailing-slash API route in AWS. The custom-authorizer route evaluation returns 403 for a trailing-slash request that the equivalent API Gateway policy accepts with 200. This discrepancy affects developers who rely on the local denial when defining wildcard resource policies, leaving the deployed route accessible beyond the tested expectation.
Summary
What happened
Incorrect authorization emulation in Serverless Offline 8.0.0 allows remote attackers to access a trailing-slash API route in AWS. The custom-authorizer route evaluation returns 403 for a trailing-slash request that the equivalent API Gateway policy accepts with 200. This discrepancy affects developers who rely on the local denial when defining wildcard resource policies, leaving the deployed route accessible beyond the tested expectation.
The record
- CVE
- CVE-2021-38384
- Published
- Aug 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-755, CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Custom Authorizer and AWS deployed stack do not have the same behaviorproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo