Skip to content

Self-Approval of Access Requests in Temporary elevated access management (TEAM) for AWS IAM Identity Center

Moderate
tawoyinfa published GHSA-x9xv-r58p-qh86 Mar 4, 2025

Package

No package listed

Affected versions

<v1.2.2

Patched versions

1.2.2

Description

Summary

Improper request input validation in Temporary Elevated Access Management (TEAM) for AWS IAM Identity Center allows a user to modify a valid request and spoof an approval in TEAM.

Impact

There is an issue in open-source Temporary Elevated Access Management (TEAM) that allows users to self-approve their own access requests by leveraging an improperly validated parameter ("approver") in the GraphQL API. This bypasses the intended validation checks, enabling users to approve their own requests even if they are not designated as eligible approvers for the requested role.

This issue could allow a user to bypass the approval mechanism when assuming a role to which they are already onboarded through TEAM. This issue cannot be leveraged to allow a user to self-approve a request to assume a role which they have not already been onboarded to through TEAM.

Impacted versions: <v1.2.2

Patches

A fix has been released in v1.2.2 for this issue and can confirm that TEAM is operating as expected.

Workarounds

Upgrade TEAM to the latest release v1.2.2. Follow instructions in updating TEAM documentation for updating process.

References

https://github.com/aws-samples/iam-identity-center-team/releases/tag/v1.2.2

Acknowledgement

We would like to thank Werner Bester, Redshift Cyber Security, for collaborating on this issue through the coordinated vulnerability disclosure process.

If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [email protected]. Please do not create a public GitHub issue.

[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

CVE ID

CVE-2025-1969

Weaknesses

No CWEs