3scale Api ManagementApplication · Redhat
CVE-2019-14852
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw was found in 3scale’s APIcast gateway that enabled the TLS 1.0 protocol. An attacker could target traffic using this weaker protocol and break its encryption, gaining access to unauthorized information. Version shipped in Red Hat 3scale API Management Platform is vulnerable to this issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe APIcast gateway in Red Hat 3scale API Management Platform has TLS 1.0 enabled, a deprecated and weak cryptographic protocol vulnerable to downgrade attacks and known cryptographic weaknesses. An attacker targeting traffic using TLS 1.0 could potentially break the encryption and access sensitive information in transit.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
3scale Api ManagementApplication
= 2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check 3scale API Management versionRun '3scale version' or check the operator deployment manifests to identify the installed version of Red Hat 3scale API ManagementAffected if The installed version is exactly 2.0
-
Locate APIcast configurationFind the APIcast gateway configuration file or environment variables. Common paths include /etc/apicast or environment variables prefixed with APICAST_ in the container/pod definitionAffected if APIcast configuration exists and TLS settings are defined
-
Inspect TLS protocol settingsExamine the APIcast configuration for 'tls_version_min', 'tls_options', or similar TLS-related settings. Look for any configuration that permits TLS 1.0 (values like 'TLSv1', 'TLSv1.0', or protocols listed without restriction to TLS 1.2+)Affected if TLS 1.0 is explicitly enabled or the minimum TLS version is set below 1.2
-
Check upstream API backend TLS settingsReview any upstream TLS configuration that APIcast uses to connect to backend services. Search for configuration parameters controlling allowed TLS versions in the APIcast gatewayAffected if Upstream connections allow TLS 1.0 or do not enforce TLS 1.2 minimum
You are affected if running Red Hat 3scale API Management version 2.0 AND TLS 1.0 is enabled or permitted in the APIcast gateway configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable TLS 1.0 in the APIcast gateway configuration and enforce TLS 1.2 or higher for all API traffic. Review and update TLS cipher suites to modern, secure configurations.
Fix this in 3scale Api Management
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14852 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14852 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data