Skip to content

FlyteAdmin Insufficient AccessToken Expiration Check

Moderate severity GitHub Reviewed Published Jul 13, 2022 in flyteorg/flyteadmin • Updated Feb 14, 2023

Package

gomod github.com/flyteorg/flyteadmin (Go)

Affected versions

< 1.1.31

Patched versions

1.1.31

Description

Impact

Authenticated users using an external identity provider can continue to use Access Tokens and ID Tokens even after they expire.
Using flyteadmin as the OAuth2 Authorization Server is unaffected by this issue.

Patches

1.1.30

Workarounds

Rotating signing keys immediately will:

  • Invalidate all open sessions,
  • Force all users to attempt to obtain new tokens.

Continue to rotate keys until flyteadmin has been upgraded,

Hide flyteadmin deployment ingress url from the internet.

References

flyteorg/flyteadmin#455

For more information

If you have any questions or comments about this advisory:

References

@EngHabu EngHabu published to flyteorg/flyteadmin Jul 13, 2022
Published by the National Vulnerability Database Jul 13, 2022
Published to the GitHub Advisory Database Jul 15, 2022
Reviewed Jul 15, 2022
Last updated Feb 14, 2023

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
High
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:H/A:N

EPSS score

0.075%
(34th percentile)

Weaknesses

CVE ID

CVE-2022-31145

GHSA ID

GHSA-qwrj-9hmp-gpxh

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.