Remote impersonation via hardcoded OAuth secret
Published Oct 6, 2022 · Updated Apr 23, 2025
Hard-coded credential vulnerability in Flyte FlyteAdmin before 1.1.44 allows remote attackers to impersonate Flyte Propeller via OAuth requests. The built-in authorization server accepts a shipped hashed client secret when staticClients remains unchanged, allowing requests to be treated as Propeller traffic. The exposure requires FlyteAdmin's internal authorization server without ExternalAuthorizationServer; attackers can then read or modify workflow-control data, while external authorization deployments are not affected.
Summary
What happened
Hard-coded credential vulnerability in Flyte FlyteAdmin before 1.1.44 allows remote attackers to impersonate Flyte Propeller via OAuth requests. The built-in authorization server accepts a shipped hashed client secret when staticClients remains unchanged, allowing requests to be treated as Propeller traffic. The exposure requires FlyteAdmin's internal authorization server without ExternalAuthorizationServer; attackers can then read or modify workflow-control data, while external authorization deployments are not affected.
The record
- CVE
- CVE-2022-39273
- Published
- Oct 6, 2022
- Updated
- Apr 23, 2025
- Vendor
- Flyte
- Product
- FlyteAdmin
- Classifications
- CWE-798, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 6, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.1.44
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo