PYSEC-2018-75
Vulnerability from pysec - Published: 2018-04-18 19:29 - Updated: 2021-08-25 04:30
VLAI?
Details
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.
Impacted products
| Name | purl | suricata-update | pkg:pypi/suricata-update |
|---|
Aliases
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "suricata-update",
"purl": "pkg:pypi/suricata-update"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.0b1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0a1"
]
}
],
"aliases": [
"CVE-2018-1000167"
],
"details": "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.",
"id": "PYSEC-2018-75",
"modified": "2021-08-25T04:30:32.993759Z",
"published": "2018-04-18T19:29:00Z",
"references": [
{
"type": "WEB",
"url": "https://tech.feedyourhead.at/content/remote-code-execution-in-suricata-update"
},
{
"type": "WEB",
"url": "https://redmine.openinfosecfoundation.org/issues/2359"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…