Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

36
Routine
HIGH 7.8UPGRADE

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 score7.8 (High)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.4% (top 63%)
CISA exploited listNo
WeaknessCWE-74
Published2017-07-17
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: plug project

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

plug project plug UPGRADE
Affected: >= 1.0.0 and < 1.0.4 · >= 1.1.0 and < 1.1.7 · >= 1.2.0 and < 1.2.3 · >= 1.3.0 and < 1.3.2
Fixed in: 1.0.4, 1.1.7, 1.2.3, 1.3.2
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy plug || rpm -q plug || plug --version
2. UPGRADE to 1.0.4 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade plug
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade plug
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison plug sudo apt install plug=<VERSION_BEFORE_1.0.0> sudo apt-mark hold plug
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list plug sudo dnf downgrade plug-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add plug
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
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

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.