TLS traffic compromise via ignored protocol restrictions
Published Mar 16, 2020 · Updated Aug 5, 2024
Algorithm downgrade in WildFly 7.2.0.GA, 7.2.3.GA, and 7.2.5.CR2 allows man-in-the-middle attackers to compromise TLS traffic. In legacy security, the OpenSSL security provider fails to enforce the configured enabled-protocols list during TLS negotiation. The affected state requires that nondefault provider and permits negotiation of a weaker protocol, exposing protected traffic to disclosure or alteration.
Summary
What happened
Algorithm downgrade in WildFly 7.2.0.GA, 7.2.3.GA, and 7.2.5.CR2 allows man-in-the-middle attackers to compromise TLS traffic. In legacy security, the OpenSSL security provider fails to enforce the configured enabled-protocols list during TLS negotiation. The affected state requires that nondefault provider and permits negotiation of a weaker protocol, exposing protected traffic to disclosure or alteration.
The record
- CVE
- CVE-2019-14887
- Published
- Mar 16, 2020
- Updated
- Aug 5, 2024
- Vendor
- 389 Directory Server
- Product
- WildFly
- Classifications
- CWE-757, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.2.0.GA, 7.2.3.GA, 7.2.5.CR2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo