Improper Certificate Validation
CVE-2025-5279
Summary
When the Amazon Redshift Python Connector is configured with the "BrowserAzureOAuth2CredentialsProvider" plugin, the driver skips the SSL certificate validation step for the Identity Provider. An insecure connection could allow an actor to intercept the token exchange process and retrieve an access token. Users should upgrade to address this issue and ensure any forked or derivative code is patched to incorporate the new fixes. This issue affects redshift-connector versions 2.0.872 through 2.1.6.
- LOW
- NETWORK
- NONE
- NONE
CWE-295 - Improper Certificate Validation
The authenticity component of a web system stems from the ability to validate “Digital certificates”, which (i) establish trust between two or more entities sharing data over a network; (ii) ensure data at rest and transit is secure from unauthorized access; and (iii) check the identity of the actors that interact with the system. An application with absent or ineffective certificate validation mechanisms allows malicious users, impersonating trusted hosts, to manipulate the communication path between the client and the host, resulting in unauthorized access to data and to the application’s internal environment, and potentially enabling man-in-the-middle attacks.
References
Advisory Timeline
- Published
