Authorization bypass through a user-controlled key in the Amazon Q Business Lambda hook sample in QnABot on AWS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| aws | qnabot-on-aws | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Aws | Qnabot-on-aws |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.333% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Authorization bypass through a user-controlled key in the optional Amazon Q Business Lambda hook sample ( q-business-lambda-hook https://github.com/aws-solutions-library-samples/qnabot-on-aws/blob/main/source/docs/lambda_hooks/README.md ), available with QnABot on AWS versions 7.0.0 through 7.4.5, might allow an authenticated remote user to read arbitrary Amazon S3 objects in the deploying AWS account. This sample solution provides an example Lambda hook and requires separate, manual deployment and additional setup. It is not deployed automatically with QnABot. Customers who have not deployed this optional sample hook are not affected and do not need to take action. To remediate this issue, affected customers should update the QnABot on AWS stack to version 7.4.6 or later and then redeploy the Amazon Q Business Lambda hook sample stack. Updating the QnABot on AWS stack alone does not deliver the fix. | |
| Title | Authorization bypass through a user-controlled key in the Amazon Q Business Lambda hook sample in QnABot on AWS | |
| First Time appeared |
Aws
Aws qnabot-on-aws |
|
| Weaknesses | CWE-639 | |
| CPEs | cpe:2.3:a:aws:qnabot-on-aws:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aws
Aws qnabot-on-aws |
|
| References |
| |
| Metrics |
cvssV3_1
|