dbcve.org
Jboss Data GridApplication · Redhat

CVE-2019-14887

CRITICAL · 9.1 CVSS v3.1 Published 2020-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A flaw was found when an OpenSSL security provider is used with Wildfly, the 'enabled-protocols' value in the Wildfly configuration isn't honored. An attacker could target the traffic sent from Wildfly and downgrade the connection to a weaker version of TLS, potentially breaking the encryption. This could lead to a leak of the data being passed over the network. Wildfly version 7.2.0.GA, 7.2.3.GA and 7.2.5.CR2 are believed to be vulnerable.

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 confidence

In Wildfly versions 7.2.0.GA, 7.2.3.GA, and 7.2.5.CR2, when an OpenSSL security provider is configured, the 'enabled-protocols' setting in the Wildfly configuration is not properly enforced. This allows an attacker to perform a TLS downgrade attack, forcing the connection to use weaker TLS versions and potentially exposing sensitive data in transit.

MitigationUpgrade Wildfly to a patched version. Alternatively, ensure TLS protocol configuration is enforced at the underlying SSL/TLS layer (OpenSSL/Java SSL context) to override the ineffective Wildfly setting.

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
Jboss Data GridApplication
Affected:= 7.0.0
Jboss Enterprise Application PlatformApplication
Affected:= 7.0.0
Jboss FuseApplication
Affected:= 7.0.0
Openshift Application RuntimesApplication
Affected:all versions
Single Sign OnApplication
Affected:= 7.0
WildflyApplication
Affected:= 7.2.0= 7.2.3= 7.2.5

CVSS 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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Wildfly installation and version
    Locate the Wildfly installation directory and check the version. In the Wildfly home, look for a version file or check the pom.xml/build.xml if source, or run 'standalone.bat --version' or 'standalone.sh --version' from the bin directory.
    Affected if The installed version is exactly 7.2.0.GA, 7.2.3.GA, or 7.2.5.CR2 (or the equivalent Red Hat versions 7.2.0, 7.2.3, 7.2.5)
  2. Verify OpenSSL security provider is configured
    Examine the Wildfly configuration file (typically standalone.xml, standalone-full.xml, or domain.xml in the configuration directory). Look for a <security-provider> or <providers> section that references OpenSSL. Also check for system properties such as 'openssl.provider' or 'security.provider' set to an OpenSSL implementation.
    Affected if An OpenSSL security provider is explicitly configured in the Wildfly configuration or via system properties
  3. Check enabled-protocols setting in configuration
    In the Wildfly configuration file, locate the SSL/TLS subsystem configuration (under <subsystem xmlns="urn:jboss:domain:undertow:..."> or similar). Look for an <ssl> or <https-listener> definition that includes an 'enabled-protocols' attribute or element specifying allowed TLS versions.
    Affected if An enabled-protocols setting exists but is configured to allow older TLS versions (such as TLS 1.0 or TLS 1.1) or the configuration relies on this setting for TLS version enforcement

The environment is affected if running Wildfly version 7.2.0, 7.2.3, or 7.2.5, OpenSSL security provider is configured, and the enabled-protocols setting in the Wildfly configuration controls TLS version enforcement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Wildfly to a patched version. Alternatively, ensure TLS protocol configuration is enforced at the underlying SSL/TLS layer (OpenSSL/Java SSL context) to override the ineffective Wildfly setting.

Fix this in Jboss Data Grid Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14887 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14887 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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