Syntastic (aka vim-syntastic) through 3.9.0 does not properly handle searches for configuration files (it searches the current directory up to potentially the root). This improper handling might be exploited for arbitrary code execution via a malicious gcc plugin, if an attacker has write access to a directory that is a parent of the base directory of the project being checked. NOTE: exploitation is more difficult after 3.8.0 because filename prediction may be needed.
References
Link | Resource |
---|---|
https://github.com/vim-syntastic/syntastic/issues/2170 | Exploit Issue Tracking Third Party Advisory |
https://github.com/vim-syntastic/syntastic/commit/6d7c0b394e001233dd09ec473fbea2002c72632f | Patch Third Party Advisory |
https://bugs.debian.org/894736 | Exploit Issue Tracking Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2018/07/msg00036.html | Mailing List Third Party Advisory |
https://www.debian.org/security/2018/dsa-4261 | Third Party Advisory |
Information
Published : 2018-05-20 13:29
Updated : 2019-10-02 17:03
NVD link : CVE-2018-11319
Mitre link : CVE-2018-11319
JSON object : View
CWE
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Products Affected
debian
- debian_linux
syntastic_project
- syntastic