Summary
Null Byte Injection in Plug.Static
Plug.Static is used for serving static assets, and is vulnerable to null
byte injection. If file upload functionality is provided, this can allow
users to bypass filetype restrictions.
We recommend all applications that provide file upload functionality and
serve those uploaded files locally with Plug.Static to upgrade immediately
or include the fix below. If uploaded files are rather stored and served
from S3 or any other cloud storage, you are not affected.
Impact
CVE-2017-1000052 has a CVSS score of 7.8 (High). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.4, 1.1.7, 1.2.3, 1.3.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
plug to 1.0.4 or later; plug to 1.1.7 or later; plug to 1.2.3 or later; plug to 1.3.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2017-1000052? CVE-2017-1000052 is a high-severity security vulnerability in plug (erlang), affecting versions < 1.0.4. It is fixed in 1.0.4, 1.1.7, 1.2.3, 1.3.2.
- How severe is CVE-2017-1000052? CVE-2017-1000052 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of plug are affected by CVE-2017-1000052? plug (erlang) versions < 1.0.4 is affected.
- Is there a fix for CVE-2017-1000052? Yes. CVE-2017-1000052 is fixed in 1.0.4, 1.1.7, 1.2.3, 1.3.2. Upgrade to this version or later.
- Is CVE-2017-1000052 exploitable, and should I be worried? Whether CVE-2017-1000052 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2017-1000052 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2017-1000052?
- Upgrade
plugto 1.0.4 or later - Upgrade
plugto 1.1.7 or later - Upgrade
plugto 1.2.3 or later - Upgrade
plugto 1.3.2 or later
- Upgrade