# CVE-2019-0231: Apache MINA SSLFilter security Issue

> Attackers can bypass SSL/TLS encryption by exploiting improper close_notify handling, allowing potential cleartext data exposure in Apache MINA applications.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2019
- **Updated:** 13 Feb 2025
- **Also known as:** DEBIAN-CVE-2019-0231, GHSA-5h29-qq92-wj7f, ROOT-APP-MAVEN-CVE-2019-0231, UBUNTU-CVE-2019-0231

## What is CVE-2019-0231?

CVE-2019-0231 is a high-severity vulnerability in Apache MINA, published on 1 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2019-0231?

4 open source packages ship an affected version, including org.apache.mina:mina-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.mina:mina-core` | Maven | All versions | 2.0.21 |
| `org.apache.mina:mina-core` | Maven | All versions | 2.0.21 |
| `org.apache.mina:mina-core` | Maven | From 2.1.0 | 2.1.1 |
| `org.apache.mina:mina-core` | Maven | From 2.1.0 | 2.1.1 |

Products: Apache Mina.

## How do I fix CVE-2019-0231?

Upgrade org.apache.mina:mina-core to a fixed version for your release line: 2.0.21 or 2.1.1.

## Is CVE-2019-0231 being exploited?

There is no known exploitation of CVE-2019-0231 in the wild and no public exploit code.

## Other vulnerabilities in Apache MINA

- [CVE-2024-52046](https://insights.sbomify.com/CVE-2024-52046/): Apache MINA: MINA applications using unbounded deserialization may allow RCE (critical 10.0)
- [CVE-2026-47065](https://insights.sbomify.com/CVE-2026-47065/): Apache MINA: Critical Deserialization Allow-list Bypass via resolveProxyClass - ZDRES-232 (critical 9.8)
- [CVE-2026-42778](https://insights.sbomify.com/CVE-2026-42778/): Apache MINA: CWE-502 Deserialization of Untrusted Data (take 2) (critical 9.8)
- [CVE-2026-42779](https://insights.sbomify.com/CVE-2026-42779/): Apache MINA vulnerable to Deserialization of Untrusted Data (CVE-2026-41635 Incomplete Fix) (critical 9.8)
- [CVE-2026-41409](https://insights.sbomify.com/CVE-2026-41409/): Apache MINA: CWE-502 Deserialization of Untrusted Data (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0231 and fix it if it is affected.

What it is: CVE-2019-0231 is a high-severity vulnerability in Apache MINA, published on 1 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0231 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.mina:mina-core (Maven): affected all versions; fixed in 2.0.21
- org.apache.mina:mina-core (Maven): affected all versions; fixed in 2.0.21
- org.apache.mina:mina-core (Maven): affected from 2.1.0; fixed in 2.1.1
- org.apache.mina:mina-core (Maven): affected from 2.1.0; fixed in 2.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-0231/ (Markdown: https://insights.sbomify.com/CVE-2019-0231/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-0231
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-0231
- OSV: https://osv.dev/vulnerability/CVE-2019-0231

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-0231/
Summaries are generated and may contain mistakes; the official description above is the record.