@hulumi/policies before 1.3.2 OIDC Trust Policy Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| hulumi | policies | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hulumi | Policies |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.512% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hulumi
Hulumi policies |
|
| Vendors & Products |
Hulumi
Hulumi policies |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | @hulumi/policies versions before 1.3.2 fail to properly validate set-qualified AWS IAM condition operators in GitHub OIDC trust policies. Attackers can use ForAnyValue:StringLike operators to hide wildcard GitHub Actions OIDC subject conditions from security guardrails. | |
| Title | @hulumi/policies before 1.3.2 OIDC Trust Policy Bypass | |
| Weaknesses | CWE-284 | |
| References |
| |
| Metrics |
cvssV3_1
|