LogstashApplication · Elastic
CVE-2016-10363
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 · uneditedLogstash versions prior to 2.3.3, when using the Netflow Codec plugin, a remote attacker crafting malicious Netflow v5, Netflow v9 or IPFIX packets could perform a denial of service attack on the Logstash instance. The errors resulting from these crafted inputs are not handled by the codec and can cause the Logstash process to exit.
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 confidenceLogstash versions before 2.3.3 using the Netflow Codec plugin are vulnerable to a denial of service attack. Remote attackers can send crafted malicious Netflow v5, Netflow v9, or IPFIX packets that cause unhandled errors in the codec, leading to the Logstash process exiting.
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
LogstashApplication
<= 2.3.2CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Check Logstash versionRun 'bin/logstash --version' or check the installed package version using your package manager (e.g., 'rpm -q logstash' or 'dpkg -l logstash')Affected if The version displayed is 2.3.2 or lower
-
Identify Netflow input usageExamine your Logstash pipeline configuration files (*.conf) in the /etc/logstash/conf.d/ directory or your configuration repository for 'netflow' or 'codec => netflow' directivesAffected if A configuration file contains a pipeline using the netflow codec or netflow input plugin
-
Verify Netflow input is exposed to networkReview the Netflow input configuration for the 'host' and 'port' settings to determine if the service is bound to a network-accessible IP address rather than localhost onlyAffected if The Netflow input is bound to a reachable network address (0.0.0.0 or non-localhost IP) and port is open to untrusted networks
-
Confirm Logstash process is runningCheck if the Logstash process is active using 'systemctl status logstash' or 'ps aux | grep logstash'Affected if Logstash is actively running and processing Netflow data from external sources
You are affected if Logstash version is 2.3.2 or lower AND the Netflow codec plugin is actively receiving packets from untrusted network sources.
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 Logstash to version 2.3.3 or later which includes proper error handling in the Netflow Codec plugin. Alternatively, restrict network access to the Netflow input to trusted sources.
Fix this in Logstash
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10363 — 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-2016-10363 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