rpm package
suse/zsh&distro=SUSE Linux Enterprise Desktop 12 SP3
pkg:rpm/suse/zsh&distro=SUSE%20Linux%20Enterprise%20Desktop%2012%20SP3
Vulnerabilities (9)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2018-1083 | Hig | 7.8 | < 5.0.5-6.7.2 | 5.0.5-6.7.2 | Mar 28, 2018 | Zsh before version 5.4.2-test-1 is vulnerable to a buffer overflow in the shell autocomplete functionality. A local unprivileged user can create a specially crafted directory path which leads to code execution in the context of the user who tries to use autocomplete to traverse t | |
| CVE-2018-1071 | Med | 5.5 | < 5.0.5-6.7.2 | 5.0.5-6.7.2 | Mar 9, 2018 | zsh through version 5.4.2 is vulnerable to a stack-based buffer overflow in the exec.c:hashcmd() function. A local attacker could exploit this to cause a denial of service. | |
| CVE-2018-7549 | Hig | 7.5 | < 5.0.5-6.7.2 | 5.0.5-6.7.2 | Feb 27, 2018 | In params.c in zsh through 5.4.2, there is a crash during a copy of an empty hash table, as demonstrated by typeset -p. | |
| CVE-2017-18206 | Cri | 9.8 | < 5.0.5-6.7.2 | 5.0.5-6.7.2 | Feb 27, 2018 | In utils.c in zsh before 5.4, symlink expansion had a buffer overflow. | |
| CVE-2017-18205 | Hig | 8.1 | < 5.0.5-6.7.2 | 5.0.5-6.7.2 | Feb 27, 2018 | In builtin.c in zsh before 5.4, when sh compatibility mode is used, there is a NULL pointer dereference during processing of the cd command with no argument if HOME is not set. | |
| CVE-2016-10714 | Cri | 9.8 | < 5.0.5-6.7.2 | 5.0.5-6.7.2 | Feb 27, 2018 | In zsh before 5.3, an off-by-one error resulted in undersized buffers that were intended to support PATH_MAX characters. | |
| CVE-2014-10072 | Cri | 9.8 | < 5.0.5-6.7.2 | 5.0.5-6.7.2 | Feb 27, 2018 | In utils.c in zsh before 5.0.6, there is a buffer overflow when scanning very long directory paths for symbolic links. | |
| CVE-2014-10071 | Cri | 9.8 | < 5.0.5-6.7.2 | 5.0.5-6.7.2 | Feb 27, 2018 | In exec.c in zsh before 5.0.7, there is a buffer overflow for very long fds in the ">& fd" syntax. | |
| CVE-2014-10070 | Hig | 7.8 | < 5.0.5-6.7.2 | 5.0.5-6.7.2 | Feb 27, 2018 | zsh before 5.0.7 allows evaluation of the initial values of integer variables imported from the environment (instead of treating them as literal numbers). That could allow local privilege escalation, under some specific and atypical conditions where zsh is being invoked in privil |
- affected < 5.0.5-6.7.2fixed 5.0.5-6.7.2
Zsh before version 5.4.2-test-1 is vulnerable to a buffer overflow in the shell autocomplete functionality. A local unprivileged user can create a specially crafted directory path which leads to code execution in the context of the user who tries to use autocomplete to traverse t
- affected < 5.0.5-6.7.2fixed 5.0.5-6.7.2
zsh through version 5.4.2 is vulnerable to a stack-based buffer overflow in the exec.c:hashcmd() function. A local attacker could exploit this to cause a denial of service.
- affected < 5.0.5-6.7.2fixed 5.0.5-6.7.2
In params.c in zsh through 5.4.2, there is a crash during a copy of an empty hash table, as demonstrated by typeset -p.
- affected < 5.0.5-6.7.2fixed 5.0.5-6.7.2
In utils.c in zsh before 5.4, symlink expansion had a buffer overflow.
- affected < 5.0.5-6.7.2fixed 5.0.5-6.7.2
In builtin.c in zsh before 5.4, when sh compatibility mode is used, there is a NULL pointer dereference during processing of the cd command with no argument if HOME is not set.
- affected < 5.0.5-6.7.2fixed 5.0.5-6.7.2
In zsh before 5.3, an off-by-one error resulted in undersized buffers that were intended to support PATH_MAX characters.
- affected < 5.0.5-6.7.2fixed 5.0.5-6.7.2
In utils.c in zsh before 5.0.6, there is a buffer overflow when scanning very long directory paths for symbolic links.
- affected < 5.0.5-6.7.2fixed 5.0.5-6.7.2
In exec.c in zsh before 5.0.7, there is a buffer overflow for very long fds in the ">& fd" syntax.
- affected < 5.0.5-6.7.2fixed 5.0.5-6.7.2
zsh before 5.0.7 allows evaluation of the initial values of integer variables imported from the environment (instead of treating them as literal numbers). That could allow local privilege escalation, under some specific and atypical conditions where zsh is being invoked in privil