Beast Attack in Cockroachdb

The Beast Attack (CVE-2014-3566) is a critical TLS 1.0/1.1 vulnerability that exploits CBC-mode cipher suites to decrypt session cookies and hijack authenticated connections. While TLS 1.3 is immune, many legacy systems and misconfigured services remain vulnerable. CockroachDB, as a distributed SQL database with built-in HTTP and SQL interfaces over TLS, can be exposed if its TLS configuration permits weak CBC ciphers.

In CockroachDB, the Beast Attack manifests through its SQL and HTTP endpoints. By default, CockroachDB attempts to use secure cipher suites, but administrators can inadvertently weaken security by:

• Custom cipher suite ordering: Using the --cipher-suites flag to prioritize CBC suites (e.g., AES128-CBC, AES256-CBC) over AEAD suites (e.g., AES128-GCM-SHA256).
• Legacy client compatibility: Allowing connections from old clients that only support CBC suites, causing the server to negotiate a vulnerable suite.
• Misconfigured load balancers/proxies: Terminating TLS upstream with weak ciphers before forwarding decrypted traffic to CockroachDB.

A successful Beast Attack against CockroachDB's SQL interface (postgresql:// or cockroach://) could allow an attacker to decrypt a session cookie or client authentication token, leading to full database compromise. For the HTTP UI (port 8080), it could expose admin session cookies.

Example vulnerable configuration (DO NOT USE):

cockroach start --certs-dir=certs --listen-addr=localhost:26257 --cipher-suites=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

This explicitly forces CBC suites. Even without this flag, if a client only offers CBC suites, CockroachDB may negotiate them if no stronger suites are mutually available.

Detecting Beast vulnerability in a CockroachDB deployment requires checking both the runtime TLS negotiation and the configuration. middleBrick's API scanner can identify this as part of its Encryption check (one of 12 parallel tests) when scanning CockroachDB's HTTP API (port 8080) or SQL interface via a proxy that exposes an HTTP endpoint. It tests for weak cipher suite negotiation.

Manual detection steps for CockroachDB:

1. Check active cipher suites using openssl against the SQL port (26257) or HTTP port (8080):

openssl s_client -connect your-cockroachdb-host:26257 -tls1 -cipher 'AES128-CBC'

If the handshake succeeds, the server accepts CBC suites. Repeat for AES256-CBC.

2. Inspect CockroachDB startup flags for --cipher-suites. Review process arguments (e.g., ps aux | grep cockroach). A list containing CBC indicates intentional weakening.

3. Review load balancer/proxy configs (HAProxy, nginx, Envoy) in front of CockroachDB. Ensure they enforce modern ciphers:

# Example HAProxy snippet ensuring no CBC
ssl-default-bind-ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384

4. Use middleBrick to scan the public-facing API endpoint (if any). For example, if the HTTP UI is exposed:

middlebrick scan https://your-cockroachdb-host:8080

The report will flag weak TLS ciphers under the Encryption category, with a severity of High if CBC suites are accepted. It maps this finding to OWASP API Top 10: A2:2019-Broken Authentication (since session hijacking leads to auth bypass) and PCI-DSS requirement 4.1 (use strong cryptography).

CockroachDB-specific indicator: The scanner may detect the Server: CockroachDB header in HTTP responses, confirming the service. A finding that references TLS_RSA_WITH_AES_128_CBC_SHA or similar CBC suites in the context of a CockroachDB endpoint is a direct indicator.

Remediation focuses on enforcing AEAD cipher suites (e.g., AES-GCM, ChaCha20-Poly1305) and disabling TLS 1.0/1.1. CockroachDB provides native controls for this.

1. Configure CockroachDB with strong cipher suites
Remove any --cipher-suites flag that includes CBC. Instead, either omit the flag (CockroachDB defaults to safe suites) or explicitly set only AEAD suites:

cockroach start \
  --certs-dir=certs \
  --listen-addr=localhost:26257 \
  --cipher-suites=TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256

Note: These are TLS 1.3 suites. For TLS 1.2 support (needed for older clients), use:

--cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

2. Disable legacy TLS versions
CockroachDB defaults to TLS 1.2+ but verify by setting minimum version:

cockroach start --min-tls-version=1.2

3. Harden load balancer/proxy in front of CockroachDB
Ensure the proxy enforces strong ciphers and TLS 1.2+ even if CockroachDB is misconfigured. Example for nginx:

ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384;
ssl_prefer_server_ciphers off;

4. Rotate certificates after changing TLS settings to ensure all connections use new parameters.

5. Verify remediation with middleBrick or openssl:

openssl s_client -connect your-cockroachdb-host:26257 -tls1_2 -cipher 'AES128-GCM'
# Should succeed
openssl s_client -connect your-cockroachdb-host:26257 -tls1 -cipher 'AES128-CBC'
# Should fail: "no cipher overlap"

Compliance impact: This fix satisfies PCI-DSS 4.0 requirement 4.1, HIPAA §164.312(e)(1) (transmission security), and GDPR Article 32 (appropriate security measures).