CVE-2018-1000167 OISF suricata-update unsafely deserializes YAML data
An insecure deserialization vulnerability in suricata-update allows remote code execution via a crafted YAML file, requiring an upgrade to the latest version.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2018-1000167?
CVE-2018-1000167 is a high-severity unsafe deserialization vulnerability in n/a, published on 18 Apr 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
OISF suricata-update version 1.0.0a1 contains an Insecure Deserialization vulnerability in the insecure yaml.load-Function as used in the following files: config.py:136, config.py:142, sources.py:99 and sources.py:131. The "list-sources"-command is affected by this bug. that can result in Remote Code Execution(even as root if suricata-update is called by root). This attack appears to be exploitable via a specially crafted yaml-file at https://www.openinfosecfoundation.org/rules/index.yaml. This vulnerability appears to have been fixed in 1.0.0b1.
Weakness: CWE-502
Which versions are affected by CVE-2018-1000167?
3 open source packages ship an affected version, including suricata-update. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
suricata-update PyPI | All versions | 1.0.0b1 |
suricata-update PyPI | All versions | 1.0.0b1 |
suricata-update PyPI | All versions | 1.0.0b1 |
Products include Oisf Suricata-Update.
How do I fix CVE-2018-1000167?
Upgrade suricata-update to 1.0.0b1 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2018-1000167 being exploited?
There is no known exploitation of CVE-2018-1000167 in the wild and no public exploit code.
Sources
Also known as GHSA-7c4h-w765-6pwg, PYSEC-2018-75.