dbcve.org
PlugApplication · Plug Project

CVE-2017-1000052

HIGH · 7.8 CVSS v3.1 Published 2017-07-17
Fix available
A fix is available. Upgrade to 1.0.4 / 1.1.7 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Elixir Plug before specified versions contains a null byte injection vulnerability in the Plug.Static module used for serving static files. Attackers can embed null bytes in file paths to bypass filetype restriction checks, potentially allowing access to sensitive files that should be restricted.

MitigationUpgrade Elixir Plug to version 1.0.4, 1.1.7, 1.2.3, 1.3.2 or later. Alternatively, validate and reject any requests containing null bytes in the filename parameter before passing to Plug.Static.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PlugApplication
Affected:>= 1.0.0, < 1.0.4>= 1.1.0, < 1.1.7>= 1.2.0, < 1.2.3>= 1.3.0, < 1.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Plug version
    Run 'mix hex.info' or check mix.lock for the Plug package version, or run 'mix deps | grep plug' in the project directory
    Affected if Version falls within ranges: 1.0.0 to <1.0.4, 1.1.0 to <1.1.7, 1.2.0 to <1.2.3, or 1.3.0 to <1.3.2
  2. Verify Plug.Static is in use
    Search the project codebase for 'Plug.Static' in router or endpoint files, typically in lib/your_app_web/router.ex or lib/your_app/endpoint.ex
    Affected if Plug.Static is being used to serve static files in the application
  3. Confirm static file serving is enabled
    Check the Plug.Static configuration in the router or endpoint for the 'at' option, for example: 'plug Plug.Static, at: "/"'
    Affected if The 'at' option is configured, enabling static file serving via Plug.Static

The environment is affected if the installed Plug version is within any of the vulnerable ranges AND Plug.Static with the 'at' option is configured to serve static files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.0.4 / 1.1.7 / 1.2.3 or later
Fixed in 1.0.41.1.71.2.3
Interim mitigation

Upgrade Elixir Plug to version 1.0.4, 1.1.7, 1.2.3, 1.3.2 or later. Alternatively, validate and reject any requests containing null bytes in the filename parameter before passing to Plug.Static.

Fix this in Plug Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000052 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000052 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data