{"answers":{"affected":"3 open source packages ship an affected version, including redshift-connector.","exploited":"There is no known exploitation of CVE-2025-5279 in the wild and no public exploit code.","fix":"Upgrade redshift-connector to 2.1.7 or later.","what":"CVE-2025-5279 is a high-severity vulnerability in Amazon Redshift, published on 27 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-5279 and fix it if it is affected.\n\nWhat it is: CVE-2025-5279 is a high-severity vulnerability in Amazon Redshift, published on 27 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-5279 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- redshift-connector (PyPI): affected from 2.0.872; fixed in 2.1.7\n- redshift-connector (PyPI): affected from 2.0.872; fixed in 2.1.7\n- redshift-connector (PyPI): affected from 2.0.872; fixed in 2.1.7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-5279/ (Markdown: https://insights.sbomify.com/CVE-2025-5279/index.md)","id":"CVE-2025-5279","markdown":"https://insights.sbomify.com/CVE-2025-5279/index.md","name":"CVE-2025-5279","record":{"aliases":["CLEANSTART-2026-GH44642","ECHO-5e25-20a4-1de0","GHSA-r244-wg5g-6w2r","MINI-3mx4-3795-g79r","PYSEC-2026-1867","ROOT-APP-PYPI-CVE-2025-5279"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Redshift Python connector","requires_auth":"none","summary":"An attacker can intercept access tokens by exploiting skipped SSL validation in the BrowserAzureOAuth2CredentialsProvider plugin of the Amazon Redshift Python connector.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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.\n\nThis 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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Issue with Amazon Redshift Python Connector and the BrowserAzureOAuth2CredentialsProvider plugin","id":"CVE-2025-5279","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"Memory corruption in Chrome","id":"CVE-2025-5280"},"packages":[{"ecosystem":"PyPI","fixed":["2.1.7"],"introduced":["2.0.872"],"last_affected":[],"package":"redshift-connector","purl":null,"source":"GHSA-r244-wg5g-6w2r"},{"ecosystem":"PyPI","fixed":["2.1.7"],"introduced":["2.0.872"],"last_affected":[],"package":"redshift-connector","purl":"pkg:pypi/redshift-connector","source":"GHSA-r244-wg5g-6w2r"},{"ecosystem":"PyPI","fixed":["2.1.7"],"introduced":["2.0.872"],"last_affected":[],"package":"redshift-connector","purl":"pkg:pypi/redshift-connector","source":"PYSEC-2026-1867"}],"prev":{"headline":"Coreutils: heap buffer under-read in gnu coreutils sort via key specification","id":"CVE-2025-5278"},"products":["Redshift"],"published":"2025-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-14","vendors":["Amazon"]},"summary":"An attacker can intercept access tokens by exploiting skipped SSL validation in the BrowserAzureOAuth2CredentialsProvider plugin of the Amazon Redshift Python connector.","url":"https://insights.sbomify.com/CVE-2025-5279/"}