New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE-2022-2385: AccessKeyID validation bypass #472
Comments
|
@micahhausler: The label(s) `/label official-cve-feed
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Hey there @micahhausler - Are you sure that is the correct CVE? When I go to NVD or other sources they are all erroring out on that ID. |
|
@micahhausler +1 to what @adcallis said. Is correct CVR mentioned or assigned? |
|
I used Mitre's new API-based reservation system, and the CVE details aren't yet published |
|
Merged CVE details in CVEProject/cvelist#6448, viewable at https://www.cve.org/CVERecord?id=CVE-2022-2385 |
CVSS Rating: High
A security issue was discovered in aws-iam-authenticator where an allow-listed IAM identity may be able to modify their username and escalate privileges.
This issue has been rated high (https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), and assigned CVE-2022-2385
Am I vulnerable?
Users are only affected if they use the AccessKeyID template parameter to construct a username and provide different levels of access based on the username.
Affected Versions
How do I mitigate this vulnerability?
Upgrading to v0.5.9 mitigates this vulnerability.
Prior to upgrading, this vulnerability can be mitigated by not using the
{{AccessKeyID}}template value to construct usernames.Fixed Versions
This issue was fixed in #469
Detection
This issue affected the logged identity, and is not discernible from valid requests.
Acknowledgements
This vulnerability was reported by Gafnit Amiga from Lightspin.
/area security
/kind bug
/committee security-response
/label official-cve-feed
The text was updated successfully, but these errors were encountered: