https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 02:20:24 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-00522 bdu:2025-00522 https://cve.radiocsirt.org/vuln/bdu:2025-00522 https://cve.radiocsirt.org/vuln/euvd-2026-254911 EUVD-2026-254911 https://cve.radiocsirt.org/vuln/euvd-2026-254911 https://cve.radiocsirt.org/vuln/fkie_cve-2024-12744 <p>A SQL injection in the Amazon Redshift JDBC Driver in v2.1.0.31 allows a user to gain escalated privileges via the getSchemas, getTables, or getColumns Metadata APIs. Users should upgrade to the driver version 2.1.0.32 or revert to driver version 2.1.0.30.</p> <p>A SQL injection in the Amazon Redshift JDBC Driver in v2.1.0.31 allows a user to gain escalated privileges via the getSchemas, getTables, or getColumns Metadata APIs. Users should upgrade to the driver version 2.1.0.32 or revert to driver version 2.1.0.30.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-12744 https://cve.radiocsirt.org/vuln/ghsa-8596-2jgr-ppj7 <p><strong>Affected:</strong> Maven: com.amazon.redshift:redshift-jdbc42</p> <p>### Summary A SQL injection in the Amazon Redshift JDBC Driver in v2.1.0.31 allows a user to gain escalated privileges via schema injection in the getSchemas, getTables, or getColumns Metadata APIs. Users should upgrade to the driver version 2.1.0.32 or revert to driver version 2.1.0.30.</p> <p>### Impact A SQL injection is possible in the Amazon Redshift JDBC Driver, version 2.1.0.31, when leveraging metadata APIs to retrieve information about database schemas, tables, or columns.</p> <p>**Impacted versions:** Amazon Redshift JDBC Driver version 2.1.0.31.</p> <p>### Patches The issue described above has been addressed in the Amazon Redshift JDBC Driver, version 2.1.0.32.</p> <p>The patch implemented in this version ensures that every metadata command input is sent to the Redshift server as part of a parameterized query, using either QUOTE_IDENT(string) or QUOTE_LITERAL(string). After processing all the inputs into quoted identifiers or literals, the metadata command is composed using these inputs and then executed on the server.</p> <p>### Workarounds Use the previous version of the Amazon Redshift JDBC Driver, 2.1.0.30.</p> <p>### References If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.</p> <p>[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting</p> <p><strong>Affected:</strong> Maven: com.amazon.redshift:redshift-jdbc42</p> <p>### Summary A SQL injection in the Amazon Redshift JDBC Driver in v2.1.0.31 allows a user to gain escalated privileges via schema injection in the getSchemas, getTables, or getColumns Metadata APIs. Users should upgrade to the driver version 2.1.0.32 or revert to driver version 2.1.0.30.</p> <p>### Impact A SQL injection is possible in the Amazon Redshift JDBC Driver, version 2.1.0.31, when leveraging metadata APIs to retrieve information about database schemas, tables, or columns.</p> <p>**Impacted versions:** Amazon Redshift JDBC Driver version 2.1.0.31.</p> <p>### Patches The issue described above has been addressed in the Amazon Redshift JDBC Driver, version 2.1.0.32.</p> <p>The patch implemented in this version ensures that every metadata command input is sent to the Redshift server as part of a parameterized query, using either QUOTE_IDENT(string) or QUOTE_LITERAL(string). After processing all the inputs into quoted identifiers or literals, the metadata command is composed using these inputs and then executed on the server.</p> <p>### Workarounds Use the previous version of the Amazon Redshift JDBC Driver, 2.1.0.30.</p> <p>### References If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.</p> <p>[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting</p> https://cve.radiocsirt.org/vuln/ghsa-8596-2jgr-ppj7