How severe is CVE-2019-0231?

CVE-2019-0231 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-0231?

CVE-2019-0231 affects the following packages: org.apache.mina:mina-core (Maven), org.apache.mina:mina-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-0231?

Update org.apache.mina:mina-core to 2.0.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0231 is resolved across your whole dependency graph.

How do I detect CVE-2019-0231 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.mina:mina-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-0231 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-0231 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-0231 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-0231?

CVE-2019-0231 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-0231?

CVE-2019-0231 is classified as CWE-319 (CWE-319). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-0231 published, and has it been updated?

CVE-2019-0231 was published on October 1, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2019-0231 — mina-core

HIGH

CVE-2019-0231 is a high-severity (CVSS 7.5) CWE-319 vulnerability in org.apache.mina:mina-core. A fix is available for org.apache.mina:mina-core — see the affected versions and patch details below.

Cleartext Transmission of Sensitive Information in Apache MINA

Also known asGHSA-5h29-qq92-wj7f

Published

Oct 1, 2019

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.apache.mina:mina-core☕org.apache.mina:mina-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.mina:mina-core`	all versions	2.0.21`org.apache.mina:mina-core:2.0.21`
☕Maven	`org.apache.mina:mina-core`	≥ 2.1.0&&< 2.1.1	2.1.1`org.apache.mina:mina-core:2.1.1`

Affected Products

1 product · 2 configurations

Application

minaapache

2 versions

2.0.202.1.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.mina:mina-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.mina:mina-core to 2.0.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0231 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

* Red Hat OpenStack Platform's OpenDaylight versions 8-10 contain the vulnerable code. However, these OpenDaylight versions were released as technical preview with limited support and will therefore not be updated. Other OpenDaylight versions do not contain the vulnerable library. * This issue affects the version of…

Product	Fixed in	Advisory
Red Hat Decision Manager 7	`mina-core`	RHSA-2020:0899
Red Hat Fuse 7.7.0	`mina-core`	RHSA-2020:3192
Red Hat Process Automation 7	`mina-core`	RHSA-2020:0895
Red Hat Satellite 6.7 for RHEL 7	`ansiblerole-foreman_scap_client-0:0.0.3-1.el7sat`	RHSA-2020:1454

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-0231 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-319CWE-319

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Oct 1, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-0231

GHSA-5h29-qq92-wj7f

References

Advisorymina.apache.org · index Advisorynvd.nist.gov · CVE 2019 0231

Related vulnerabilities

Also affects mina-core

This CVE is high severity; 6 of 7 other CVEs affecting mina-core are rated as high or higher (top: critical).

CVE-2026-47065CVE-2026-42778CVE-2026-42779CVE-2026-41635CVE-2026-41409CVE-2024-52046CVE-2021-41973

Same weakness: CWE-319

This CVE is high severity — higher than any of the other 1 CVE with CWE-319 (highest there: low).

CVE-2026-114614Browse all CWE-319

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-0231 — mina-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2019-0231 in your dependencies?