CVE-2014-10070: zsh before 5.0.7 allows evaluation of the initial values of integer variables imported from the environment (instead of treating them as…
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: zsh (Debian:12) 5.0.7-3; zsh (Debian:7) 4.3.17-1+deb7u1; zsh (SUSE:Linux Enterprise Desktop 12 SP3) 5.0.5-6.7.2.
Low priority for now. Upgrade to zsh (Debian:12) 5.0.7-3; zsh (Debian:7) 4.3.17-1+deb7u1; zsh (SUSE:Linux Enterprise Desktop 12 SP3) 5.0.5-6.7.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 privilege-elevation contexts when the environment has not been properly sanitized, such as when zsh is invoked by sudo on systems where "env_reset" has been disabled.
- Published
- Feb 27, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 42th percentile
- CWE
- CWE-264
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zsh project | zsh | cpe:2.3:a:zsh_project:zsh |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zsh project zshup to 5.0.6 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | zsh | before 5.0.7-3 | 5.0.7-3 |
| Debian:7 | zsh | before 4.3.17-1+deb7u1 | 4.3.17-1+deb7u1 |
| SUSE:Linux Enterprise Desktop 12 SP3 | zsh | before 5.0.5-6.7.2 | 5.0.5-6.7.2 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | zsh | before 4.3.6-67.9.8.1 | 4.3.6-67.9.8.1 |
Same product
zsh project: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-10072In utils.c in zsh before 5.0.6, there is a buffer overflow when scanning very long directory paths for symbolic links.40Plan
- CVE-2017-18205In 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…33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:zsh | 5.0.7-3 · Debian:12 | Package registry (OSV) |
| suse:zsh | 5.0.5-6.7.2 · SUSE:Linux Enterprise Desktop 12 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.