Access-token theft via unchecked IdP certificates
Published May 27, 2025 · Updated Oct 14, 2025
Improper certificate validation in Amazon Redshift Python Connector 2.0.872 through 2.1.6 allows man-in-the-middle attackers to steal access tokens. With BrowserAzureOAuth2CredentialsProvider configured, the driver leaves Identity Provider TLS certificates unchecked during token exchange. An attacker must control or intercept the network path to impersonate the Identity Provider; the bounded consequence is exposure of the exchanged access token.
Summary
What happened
Improper certificate validation in Amazon Redshift Python Connector 2.0.872 through 2.1.6 allows man-in-the-middle attackers to steal access tokens. With BrowserAzureOAuth2CredentialsProvider configured, the driver leaves Identity Provider TLS certificates unchecked during token exchange. An attacker must control or intercept the network path to impersonate the Identity Provider; the bounded consequence is exposure of the exchanged access token.
The record
- CVE
- CVE-2025-5279
- Published
- May 27, 2025
- Updated
- Oct 14, 2025
- Vendor
- Amazon Web Services
- Product
- Amazon Redshift
- Classifications
- CWE-295, CAPEC-475, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 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=2.0.872 <2.1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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