MinaApplication · Apache
CVE-2019-0231
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 · uneditedHandling 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.
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 confidenceIn Apache MINA, the SSL/TLS close_notify alert message is not properly handled - the connection socket remains open after receiving close_notify instead of being closed. This can cause the client to potentially receive cleartext (unencrypted) messages after the TLS session is supposed to have ended, breaking the confidentiality guarantee of TLS and allowing information disclosure.
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
MinaApplication
= 2.0.20= 2.1.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache MINA versionCheck your project dependencies (pom.xml, build.gradle, or MANIFEST.MF in mina-core.jar) for the exact Apache MINA version numberAffected if The installed version is exactly 2.0.20 or 2.1.0
-
Confirm SSL/TLS usageInspect your application code and configuration for NioSocketConnector or NioServerSocketConnector with SslFilter enabled, or any MINA-based SSL/TLS session setupAffected if Your application uses MINA with SSL/TLS encryption enabled
-
Verify session handling behaviorMonitor network traffic during TLS close handshake - observe whether the server sends close_notify and whether the connection is properly terminated vs remaining openAffected if After receiving close_notify alert, the socket connection remains in an open state rather than being closed cleanly
-
Check for potential cleartext leakageCapture and inspect network packets after TLS session termination - verify no unencrypted data is transmitted after the close_notify alertAffected if Cleartext application data is transmitted or received after the TLS close_notify has been sent
You are affected if your application runs Apache MINA version 2.0.20 or 2.1.0 with SSL/TLS enabled, and the TLS session does not properly terminate the socket upon receiving close_notify.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Apache MINA to version 2.0.21 or 2.1.1 (from 2.0.20 or 2.1.0 respectively) to remediate this SSL/TLS close_notify handling vulnerability.
Fix this in Mina
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0231 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-0231 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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