Threat database

Improper certificate validation in the identity provider connection components in Amazon Athena ODBC driver before 2.1.0.0 might allow a man-in-the-middle threat actor to intercept authentication credentials due to insufficient default transport security when connecting to identity providers. This only applies to connections with external identity providers and does not apply to connections with Athena. To remediate this issue, users should upgrade to version 2.1.0.0.

An uninitialized stack read issue exists in Amazon Ion-C versions <v1.1.4 that may allow a threat actor to craft data and serialize it to Ion text in such a way that sensitive data in memory could be exposed through UTF-8 escape sequences. To mitigate this issue, users should upgrade to version v1.1.4.

CVE-2025-12779 is a vulnerability in the Amazon WorkSpaces client for Linux versions 2023.0 through 2024.8. It involves improper handling of authentication tokens, which may allow local users on the same machine to access another user's authentication token and thereby access their WorkSpace. The issue is resolved by upgrading to version 2025.0 or later.

CVE-2025-11573 is a high-severity vulnerability in the Amazon.IonDotnet library versions prior to 1.3.2. It involves improper validation of syntactic correctness of input, which can cause an infinite loop when processing specially crafted text input. This results in a denial of service condition. The library has been deprecated as of August 20, 2025, and no further updates will be provided beyond version 1.3.2.

We identified an issue in the Amazon ECS agent where, under certain conditions, an introspection server could be accessed off-host by another instance if the instances are in the same security group or if their security groups allow incoming connections that include the port where the server is hosted. This issue does not affect instances where the option to allow off-host access to the introspection server is set to 'false'. This issue has been addressed in ECS agent version 1.97.1. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. If customers cannot update to the latest AMI, they can modify the Amazon EC2 security groups to restrict incoming access to the introspection server port (51678).

CVE-2025-8904 is a critical vulnerability in Amazon EMR where the Secret Agent component stores Kerberos credentials in a keytab file within the /tmp/ directory. This file can be accessed by users with access to /tmp/ and another account, potentially allowing decryption of keys and privilege escalation. The issue affects Amazon EMR versions from 6.10 up to but not including 7.4. Users are advised to upgrade to version 7.5 or higher or apply provided fixes for versions between 6.10 and 7.4.

The Amazon Q Developer Visual Studio Code extension version 1.84.0 contains embedded inert malicious code intended to invoke the Q Developer CLI. However, a syntax error in this code prevents successful execution of API calls, limiting the vulnerability's impact. This issue is classified under CWE-506 (Embedded Malicious Code) and has a medium severity with a CVSS score of 5.1. Users should upgrade to version 1.85.0 and remove all installations of version 1.84.

CVE-2025-6031 is a high-severity vulnerability in the Amazon Cloud Cam home security camera, which has been deprecated and is no longer supported since December 2, 2022. The device attempts to connect to a deprecated remote service infrastructure upon powering on. It defaults to a pairing mode that allows an arbitrary user to bypass SSL pinning and associate the device with an arbitrary network, enabling interception and modification of network traffic. Customers are advised to discontinue use of any remaining Amazon Cloud Cam devices.

We have identified a buffer overflow issue allowing out-of-bounds write when processing LLMNR or mDNS queries with very long DNS names. This issue only affects systems using Buffer Allocation Scheme 1 with LLMNR or mDNS enabled. Users should upgrade to the latest version and ensure any forked or derivative code is patched to incorporate the new fixes.

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.

An issue in the native clients for Amazon WorkSpaces (when running PCoIP protocol) may allow an attacker to access remote sessions via man-in-the-middle.

An issue in the native clients for Amazon WorkSpaces (when running Amazon DCV protocol), Amazon AppStream 2.0, and Amazon DCV Clients may allow an attacker to access remote sessions via man-in-the-middle.

A SQL injection in the Amazon Redshift ODBC Driver v2.1.5.0 (Windows or Linux) allows a user to gain escalated privileges via the SQLTables or SQLColumns Metadata APIs. Users are recommended to upgrade to the driver version 2.1.6.0 or revert to driver version 2.1.4.0.

A SQL injection in the Amazon Redshift Python Connector v2.1.4 allows a user to gain escalated privileges via the get_schemas, get_tables, or get_columns Metadata APIs. Users are recommended to upgrade to the driver version 2.1.5 or revert to driver version 2.1.3.

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.

A data.all admin team member who has access to the customer-owned AWS Account where data.all is deployed may be able to extract user data from data.all application logs in data.all via CloudWatch log scanning for particular operations that interact with customer producer teams data.

Due to inconsistent authorization permissions, data.all may allow an external actor with an authenticated account to perform restricted operations against DataSets and Environments.

An authenticated data.all user is able to manipulate a getDataset query to fetch additional information regarding the parent Environment resource that the user otherwise would not able to fetch by directly querying the object via getEnvironment in data.all.

An authenticated data.all user is able to perform mutating UPDATE operations on persisted Notification records in data.all for group notifications that their user is not a member of.

Authentication tokens issued via Cognito in data.all are not invalidated on log out, allowing for previously authenticated user to continue execution of authorized API Requests until token is expired.