CVE-2019-0231 json
Apache MINA SSLFilter security Issue
published 7y ago modified 4mo ago also GHSA-5h29-qq92-wj7f , EUVD-2022-2588
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
Handling of the close_notify SSL/TLS message does not lead to a connection closure, leading the server to retain the socket opened and to have the client potentially receive clear text messages afterward. Mitigation: 2.0.20 users should migrate to 2.0.21, 2.1.0 users should migrate to 2.1.1. This issue affects: Apache MINA.
Patch / fix
- maven org.apache.mina:mina-core 2.0.21, 2.1.1
- mina2 Debian 14, Debian 13, Debian 12 2.1.4-1
debian advisories DEBIAN-CVE-2019-0231
- tfm satellite capsule 6.7, satellite 6.7 5.0-9.el7sat
- kobo satellite capsule 6.7, satellite 6.7 0.5.1-1.el7sat
- pulp satellite capsule 6.7, satellite 6.7 2.21.0-1.el7sat
- gofer satellite capsule 6.7, satellite 6.7 2.12.5-7.el7sat
- future satellite capsule 6.7, satellite 6.7 0.16.0-11.el7sat
- ostree satellite capsule 6.7, satellite 6.7 2017.1-2.atomic.el7
- foreman satellite capsule 6.7, satellite 6.7 1.24.1.21-1.el7sat
- katello satellite capsule 6.7, satellite 6.7 3.14.0-6.el7sat
red hat advisories RHSA-2020:1454
Is CVE-2019-0231 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-0231 updated cvss 6.8
mina-core: Retaining an open socket in close_notify SSL-TLS leading to Information disclosure.
-
Red Hat BPM Suite 6 mina-core Red Hat JBoss A-MQ 6 mina-core Red Hat JBoss BRMS 5 mina-core Red Hat JBoss BRMS 6 mina-core Red Hat JBoss Data Virtualization 6 mina-core Red Hat JBoss Fuse 6 mina-coreaffected: no fix planned “Out of support scope”
+2 more productsfewer
Red Hat JBoss Fuse Service Works 6 mina-core Red Hat JBoss SOA Platform 5 mina-core -
Red Hat OpenStack Platform 8 (Liberty) opendaylight Red Hat OpenStack Platform 9 (Mitaka) opendaylight Red Hat OpenStack Platform 10 (Newton) opendaylight Red Hat Storage 3 rhevm-dependenciesaffected: no fix planned “Will not fix”
-
Red Hat Decision Manager 7fixed: vendor fix RHSA-2020:0899
-
Red Hat Fuse 7.7.0fixed: vendor fix RHSA-2020:3192
-
Red Hat Process Automation 7fixed: vendor fix RHSA-2020:0895
-
Red Hat Satellite 6.7 tfm 5.0-9.el7sat, kobo 0.5.1-1.el7sat, pulp 2.21.0-1.el7sat, gofer 2.12.5-7.el7sat, receptor 0.6.1-1.el7ar, tfm-ror52 1.0-4.el7sat, +498 more Red Hat Satellite Capsule 6.7 tfm 5.0-9.el7sat, kobo 0.5.1-1.el7sat, pulp 2.21.0-1.el7sat, gofer 2.12.5-7.el7sat, tfm-ror52 1.0-4.el7sat, future 0.16.0-11.el7sat, +241 morefixed: vendor fix RHSA-2020:1454
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.13% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.mina:mina-core | <2.0.21 >=2.1.0, <2.1.1 |
2.0.21 2.1.1 |
Affected products
- Apache Software Foundation Apache MINA
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
mina.apache.org
/mina-project/index.html#mina-211-mina-2021-released-posted-on-april-14-2019
web, release-notes, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-0231
advisory
Sources
- CVE List CVE-2019-0231
- GitHub Advisory GHSA-5h29-qq92-wj7f
- NVD CVE-2019-0231
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.