Improper Certificate ValidationWeakness · CWE-295

CVE-2025-5279

HIGH · 7.0 CVSS v4.0 Published 2025-05-27

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

79/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · high confidence

The Amazon Redshift Python Connector's BrowserAzureOAuth2CredentialsProvider plugin skips SSL certificate validation when connecting to the Identity Provider, allowing man-in-the-middle attackers to intercept OAuth token exchanges and steal access tokens.

MitigationUpgrade Amazon Redshift Python Connector to version 2.1.7 or later to restore proper SSL certificate validation for Azure OAuth connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
Authentication: X
User interaction: None
Scope: X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check installed version of Amazon Redshift Python Connector

Run `pip show amazon-redshift-python-connector` or in Python: `import redshift_connector; print(redshift_connector.__version__)`

Affected if Version is lower than 2.1.7
Identify if Azure OAuth is being used

Search codebase or configuration for 'BrowserAzureOAuth2CredentialsProvider' or Azure-related OAuth settings in your connection code or config files

Affected if BrowserAzureOAuth2CredentialsProvider is explicitly configured as the credential provider
Verify OAuth connection method in use

Inspect connection code that initializes the Redshift connector - look for `credential_provider` parameter set to BrowserAzureOAuth2CredentialsProvider

Affected if The application uses BrowserAzureOAuth2CredentialsProvider for authentication to Redshift with Azure AD
Review SSL verification in OAuth flow

Check if ssl_verify, cert, or sslmode parameters are set to False, disabled, or bypassed in the connection or environment configuration for Azure OAuth

Affected if SSL certificate validation is explicitly disabled for the OAuth identity provider connection

Environment is affected if Amazon Redshift Python Connector version is below 2.1.7 AND BrowserAzureOAuth2CredentialsProvider is being used for Azure AD authentication, regardless of SSL verification settings, since the vulnerability is in the plugin itself.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade Amazon Redshift Python Connector to version 2.1.7 or later to restore proper SSL certificate validation for Azure OAuth connections.

Recommended fix High confidence

2.1.7

Check current installed version of the Amazon Redshift Python Connector using: pip show amazon-redshift-python-connector
Upgrade to version 2.1.7 or later: pip install --upgrade amazon-redshift-python-connector>=2.1.7
Verify the upgrade was successful: pip show amazon-redshift-python-connector and confirm the version is 2.1.7 or higher
If using BrowserAzureOAuth2CredentialsProvider in existing code, test the OAuth flow to confirm SSL certificate validation is now enforced

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation1.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

5.0 hours of engineering $860

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-5279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5279 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-5279?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 7.0 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 5 hrs · Low

Typical engagement from $860

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-5279 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References