CVE-2018-1000167

Name: CVE-2018-1000167
Creator: NVD / NIST
Published: 2018-04-18T19:29:00.833+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 4.16%

Last modified Jun 17, 2026

CVE-2018-1000167 is a vulnerability of currently unknown severity. 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. EPSS estimates a 4.16% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability

4.16%

89.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-502

Affected Software

Vendor	Product	Versions
Oisf	Suricata-Update	1.0.0a1

References

https://redmine.openinfosecfoundation.org/issues/2359Third Party Advisory
https://tech.feedyourhead.at/content/remote-code-execution-in-suricata-updateExploit, Third Party Advisory
https://redmine.openinfosecfoundation.org/issues/2359Third Party Advisory
https://tech.feedyourhead.at/content/remote-code-execution-in-suricata-updateExploit, Third Party Advisory

Timeline

Published: Apr 18, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2018-1000167?

How severe is CVE-2018-1000167?

Severity scoring for CVE-2018-1000167 is pending analysis. The EPSS model estimates a 4.16% probability of exploitation in the next 30 days.

How do I fix CVE-2018-1000167?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2018-1000167?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST