CVE-2016-1000222
First published: Fri Jun 16 2017(Updated: )
Logstash prior to version 2.1.2, the CSV output can be attacked via engineered input that will create malicious formulas in the CSV data.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Logstash Management API | <=2.1.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-1000222?
CVE-2016-1000222 is classified as a medium severity vulnerability.
How do I fix CVE-2016-1000222?
To fix CVE-2016-1000222, upgrade to Logstash version 2.1.2 or later.
What kind of attacks does CVE-2016-1000222 enable?
CVE-2016-1000222 enables attacks that exploit CSV output to inject malicious formulas.
Which versions of Logstash are affected by CVE-2016-1000222?
CVE-2016-1000222 affects Logstash versions prior to 2.1.2.
How can I mitigate risks associated with CVE-2016-1000222?
Mitigation of CVE-2016-1000222 can be achieved by avoiding the use of untrusted CSV data in Logstash.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/references
- agent/weakness
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/elastic
- canonical/logstash management api
- version/logstash management api/2.1.1