| CCC.RDMS.TH01 | Unauthorized Access via Default Credentials | If default credentials are not disabled or changed, unauthorized access may be gained to the RDMS environment. This may lead to data breaches, data manipulation, or overall compromise of the database instance. | 1 | 1 | 1 |
| CCC.RDMS.TH02 | Brute Force Attempts on Database Authentication | Repeated attempts to guess database user passwords may be made through brute force techniques. This condition could result in unauthorized access if successful, compromising database security and sensitive information. Attempts arrive over whichever IPv4 or IPv6 endpoint the network access rules leave reachable. | 1 | 1 | 1 |
| CCC.RDMS.TH04 | Unintentional Database Backup Restoration | A database backup may be restored unintentionally, potentially leading to the loss or overwrite of current data. This condition could disrupt operations and result in data inconsistency or corruption. | 1 | 1 | 1 |
| CCC.RDMS.TH05 | Unauthorized Snapshot Sharing | Snapshots may be shared with untrusted accounts, which can lead to unauthorized access and potential data exfiltration. This significantly increases the risk of data exposure if sensitive information is contained in the snapshots. | 1 | 1 | 1 |
| CCC.RDMS.TH06 | Database Engine Runs with Known Vulnerabilities | Automated engine patching may be disabled, or maintenance windows may be deferred indefinitely, so the database engine continues to run a version with published vulnerabilities. Those vulnerabilities can be exploited by any client able to reach the engine, compromising the confidentiality, integrity, and availability of the database. | 0 | 1 | 1 |
| CCC.RDMS.TH07 | Excessive Privileges are Granted Within the Database | Database roles and grants inside the engine may be configured more broadly than required, such as application users holding administrative roles or schemas readable by every login. Any authenticated user can then read or modify data beyond their function, impacting the confidentiality and integrity of all data in the instance. | 0 | 1 | 1 |
| CCC.RDMS.TH08 | Long-lived Database Credentials are Exposed | Static usernames and passwords may be stored in application configuration, connection strings, or source repositories and remain valid for long periods. When such a credential is disclosed it can be reused by an unauthorized party until it is rotated, impacting the confidentiality and integrity of the database. | 0 | 1 | 1 |
| CCC.RDMS.TH09 | Session State Leaks Between Pooled Connections | A managed connection pool may reuse a server session for successive clients without resetting session-level state such as temporary tables, prepared statements, or an assumed role. State set by one client can then be read or acted on by another, impacting the confidentiality and integrity of data and obscuring which client performed an action. | 0 | 1 | 1 |
| CCC.RDMS.TH11 | Read Replicas are Deployed with Weaker Protections | A read replica may be created with network access rules or public accessibility that differ from the primary. The same data is then reachable through the replica under weaker protection, impacting its confidentiality. | 0 | 1 | 1 |
| CCC.RDMS.TH12 | Failover Causes Data Loss or Divergent Writes | When the standby is promoted while replication lags, transactions committed on the primary may be absent from the new primary, and a former primary that keeps accepting writes produces two divergent copies. This impacts the integrity and availability of the data and can defeat recovery. | 0 | 1 | 1 |