CVE-2019-15699
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 · uneditedAn issue was discovered in app-layer-ssl.c in Suricata 4.1.4. Upon receiving a corrupted SSLv3 (TLS 1.2) packet, the parser function TLSDecodeHSHelloExtensions tries to access a memory region that is not allocated, because the expected length of HSHelloExtensions does not match the real length of the HSHelloExtensions part of the packet.
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 Suricata 4.1.4, the TLSDecodeHSHelloExtensions function in app-layer-ssl.c lacks proper bounds validation when processing SSLv3/TLS 1.2 packets. When a corrupted packet declares an HSHelloExtensions length that doesn't match the actual data available, the parser attempts to read from an unallocated memory region, causing an out-of-bounds read vulnerability.
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= 4.1.4CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
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 Suricata installation and versionRun `suricata --version` to confirm the installed version of SuricataAffected if Version displayed is 4.1.4 exactly
-
Verify SSL/TLS protocol parsing is enabledCheck the suricata.yaml configuration file for `app-layer.protocols.tls.enabled` setting (typically in /etc/suricata/suricata.yaml or similar)Affected if TLS parsing is set to `enabled: true` or not explicitly disabled
-
Confirm SSL detection is configured for the expected trafficInspect the `app-layer.protocols.tls.-detection-ports` configuration to see which ports are configured for SSL/TLS inspectionAffected if Ports are configured and traffic on those ports would reach Suricata (e.g., port 443)
You are affected only if Suricata version 4.1.4 is running AND SSL/TLS protocol parsing is enabled and processing traffic on configured ports.
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.
dbcve · scopedUpgrade to Suricata 4.1.5 or later. Alternatively, implement network-level filtering to drop malformed SSL/TLS handshake packets before they reach the Suricata instance.
Suricata 5.0.x (or latest stable 4.1.x above 4.1.4)
- 1. Back up your current Suricata configuration files (e.g., suricata.yaml, classification.config, threshold.config)
- 2. Stop the Suricata service
- 3. Obtain Suricata 5.0.x or the latest stable 4.1.x release from the official repository (https://suricata.io/download/)
- 4. Install the new version following standard upgrade procedures
- 5. Restore your configuration files from the backup
- 6. Validate configuration syntax: `suricata --test-config`
- 7. Start the Suricata service and verify normal operation
- 8. Monitor logs for any errors related to SSL/TLS parsing
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15699 — 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-15699 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