{ "CVE_data_meta": { "ASSIGNER": "cve@mitre.org", "ID": "CVE-2023-35852", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "n/a", "version": { "version_data": [ { "version_value": "n/a" } ] } } ] }, "vendor_name": "n/a" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "In Suricata before 6.0.13 (when there is an adversary who controls an external source of rules), a dataset filename, that comes from a rule, may trigger absolute or relative directory traversal, and lead to write access to a local filesystem. This is addressed in 6.0.13 by requiring allow-absolute-filenames and allow-write (in the datasets rules configuration section) if an installation requires traversal/writing in this situation." } ] }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "n/a" } ] } ] }, "references": { "reference_data": [ { "url": "https://github.com/OISF/suricata/compare/suricata-6.0.12...suricata-6.0.13", "refsource": "MISC", "name": "https://github.com/OISF/suricata/compare/suricata-6.0.12...suricata-6.0.13" }, { "url": "https://github.com/OISF/suricata/commit/aee1523b4591430ebed1ded0bb95508e6717a335", "refsource": "MISC", "name": "https://github.com/OISF/suricata/commit/aee1523b4591430ebed1ded0bb95508e6717a335" }, { "url": "https://github.com/OISF/suricata/commit/735f5aa9ca3b28cfacc7a443f93a44387fbacf17", "refsource": "MISC", "name": "https://github.com/OISF/suricata/commit/735f5aa9ca3b28cfacc7a443f93a44387fbacf17" }, { "url": "https://www.stamus-networks.com/stamus-labs", "refsource": "MISC", "name": "https://www.stamus-networks.com/stamus-labs" } ] } }