CVE-2019-14852

7.5 HIGH

📋 TL;DR

CVE-2019-14852 is a cryptographic vulnerability in 3scale's APIcast gateway that allows TLS 1.0 protocol usage, enabling attackers to potentially decrypt sensitive API traffic. This affects Red Hat 3scale API Management Platform deployments using vulnerable APIcast versions. Organizations transmitting sensitive data through these gateways are at risk of data exposure.

💻 Affected Systems

Products:
  • Red Hat 3scale API Management Platform
Versions: APIcast versions prior to the fix
Operating Systems: Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects deployments using APIcast gateway component with TLS 1.0 enabled

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers intercept and decrypt all API traffic passing through the gateway, exposing authentication tokens, personal data, and business-critical information.

🟠

Likely Case

Selective decryption of sensitive API calls containing authentication credentials or personal identifiable information.

🟢

If Mitigated

No data exposure if TLS 1.0 is disabled and modern protocols are enforced.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Requires man-in-the-middle position and TLS 1.0 downgrade capability

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Updated APIcast versions from Red Hat

Vendor Advisory: https://bugzilla.redhat.com/show_bug.cgi?id=1758208

Restart Required: Yes

Instructions:

1. Update APIcast to patched version via Red Hat channels. 2. Restart APIcast service. 3. Verify TLS 1.0 is disabled in configuration.

🔧 Temporary Workarounds

Disable TLS 1.0 in APIcast configuration

linux

Manually configure APIcast to disable TLS 1.0 and enforce TLS 1.2 or higher

Edit APIcast configuration to set ssl_protocols: TLSv1.2 TLSv1.3
Restart APIcast service

🧯 If You Can't Patch

  • Implement network-level TLS inspection to block TLS 1.0 connections
  • Use API gateway load balancer to enforce modern TLS protocols

🔍 How to Verify

Check if Vulnerable:

Check APIcast configuration for TLS 1.0 support and test with openssl s_client -connect <gateway>:<port> -tls1

Check Version:

apicast --version or check container/pod version

Verify Fix Applied:

Confirm TLS 1.0 connections fail and only TLS 1.2+ connections succeed

📡 Detection & Monitoring

Log Indicators:

  • TLS 1.0 handshake attempts in APIcast logs
  • Unexpected protocol negotiation events

Network Indicators:

  • TLS 1.0 ClientHello packets to APIcast endpoints
  • Successful TLS 1.0 sessions

SIEM Query:

source="apicast" AND "TLSv1" OR "TLS 1.0"

🔗 References

📤 Share & Export