cve.bz

CVE-2025-5279 amazon redshift: Improper Certificate Validation

7.0 highEPSS 0.3%Fix available

High (7.0) in amazon redshift. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in redshift-connector 2.1.7.

On this page
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. This issue has been addressed in driver version 2.1.7. Users should upgrade to address this issue and ensure any forked or derivative code is patched to incorporate the new fixes.

Severity

CVSS 4.0

7.0 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-05-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • redshift-connector (PyPI): fixed in 2.1.7

Ask an AI about this CVE

Show the promptExplain CVE-2025-5279 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-5279?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-5279?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-5279 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Amazon Redshiftfrom 2.0.872 before 2.1.7

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r244-wg5g-6w2rPyPIredshift-connector>=2.0.872 <2.1.72.1.7
PYSEC-2026-1867PyPIredshift-connector>=2.0.872 <2.1.72.1.7

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an IMPORTANT severity because this vulnerability exists in the Amazon Redshift Python Connector, when configured with the BrowserAzureOAuth2CredentialsProvider plugin, this issue arises because the driver skips the SSL certificate validation step for the Identity Provider during the token exchange process, an insecure connection could allow an attacker to intercept communications and retrieve an access token.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-5279.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON