CVE-2017-1000052: Elixir Plug before v1.0.4, v1.1.7, v1.2.3 and v1.3.2 is vulnerable to null byte injection in the Plug.Static c
CVE-2017-1000052 is a high-severity flaw (CVSS 7.8) affecting plug. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Elixir Plug before v1.0.4, v1.1.7, v1.2.3 and v1.3.2 is vulnerable to null byte injection in the Plug.Static component, which may allow users to bypass filetype restrictions.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.8 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.4% (top 63%) |
| CISA exploited list | No |
| Weakness | CWE-74 |
| Published | 2017-07-17 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-1000052?
plug: upgrade to 1.0.4, 1.1.7, 1.2.3, 1.3.2. Exact commands for each OS are on this page.
Is CVE-2017-1000052 being exploited?
CVE-2017-1000052 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2017-1000052 affect?
CVE-2017-1000052 affects plug. Severity is high (CVSS 7.8). Elixir Plug before v1.0.4, v1.1.7, v1.2.3 and v1.3.2 is vulnerable to null byte injection in the Plug.Static component, which may allow users to bypass filetype restrictions.
How urgent is CVE-2017-1000052?
Priority 36/100. High severity
Related CVEs
- CVE-2018-1000883 MEDIUM 6.5 UPGRADE Elixir Plug Plug version All contains a Header Injection vulnerability in Connection that can result in Given
- CVE-2017-1000053 HIGH 8.1 UPGRADE Elixir Plug before v1.0.4, v1.1.7, v1.2.3 and v1.3.2 is vulnerable to arbitrary code execution in the deserial