CVE-2016-3715
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 · uneditedThe EPHEMERAL coder in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allows remote attackers to delete arbitrary files via a crafted image.
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 confidenceThe EPHEMERAL coder in ImageMagick allows remote attackers to delete arbitrary files on the system by providing a specially crafted image file containing a path to the file to be deleted. This occurs because the coder processes instructions embedded in the image that specify file deletion without proper path sanitization, enabling path traversal attacks.
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= 6.0= 7.0= 6.7= 7.2= 7.3= 7.4= 7.5= 7.6= 7.7= 6.0_s390x= 7.0_s390x= 6.7_s390x= 7.2_s390x= 7.3_s390x= 7.4_s390x= 7.5_s390x= 7.6_s390x= 7.7_s390x= 6.0_ppc64= 7.0_ppc64= 6.7_ppc64= 7.2_ppc64= 7.3_ppc64= 7.4_ppc64= 7.5_ppc64= 7.6_ppc64= 7.7_ppc64= 7.0_ppc64le= 7.2_ppc64le= 7.3_ppc64le= 7.4_ppc64le= 7.5_ppc64le= 7.6_ppc64le= 7.7_ppc64leCVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify ImageMagick versionRun 'rpm -q ImageMagick' on RHEL-based systems, or 'convert -version' to see the version numberAffected if The installed version falls within the affected RHEL versions listed (6.0, 6.7, 7.0-7.7 across all architectures)
-
Locate the EPHEMERAL coderFind the coders directory - typically /usr/lib64/ImageMagick-*//modules-Q16/coders/ or /usr/lib/ImageMagick-*/modules/coders/. Check for a file named 'ephemeral.so' or 'EPHEMERAL.la'Affected if The EPHEMERAL coder binary exists in the ImageMagick coders directory
-
Check ImageMagick policy configurationExamine /etc/ImageMagick/policy.xml or the equivalent policy file. Look for a '<coder>' or '<policy>' entry that restricts or allows the EPHEMERAL coderAffected if No restriction exists for the EPHEMERAL coder, or the policy explicitly allows it
-
Test if EPHEMERAL coder loadsRun 'identify -list configure | grep DELEGATES' to see enabled delegates, or attempt to process a file that triggers the EPHEMERAL coderAffected if The EPHEMERAL coder is operational and can process image files with embedded deletion instructions
You are affected if ImageMagick is installed at a vulnerable RHEL version listed in the advisory AND the EPHEMERAL coder is present and not disabled in the ImageMagick policy configuration.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade ImageMagick to version 6.9.3-10 or later (7.x to 7.0.1-1 or later). If immediate patching is not feasible, disable the EPHEMERAL coder in ImageMagick's policy configuration or ensure untrusted images are not processed without proper sandboxing and input validation.
ImageMagick 6.9.3-10+ or 7.0.1-1+
- Update the system package cache: yum check-update or dnf check-update
- Install the updated ImageMagick package: yum update ImageMagick or dnf update ImageMagick
- Restart any services that use ImageMagick to ensure the new version is loaded
- Verify the installed version is 6.9.3-10 or later for ImageMagick 6.x, or 7.0.1-1 or later for ImageMagick 7.x using: rpm -q ImageMagick
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3715 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- git.imagemagick.org
- www.exploit-db.com
- www.imagemagick.org
- git.imagemagick.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- www.debian.org
- www.debian.org
- www.openwall.com
- www.oracle.com
- www.oracle.com
- www.securityfocus.com
- www.securityfocus.com
- www.slackware.com
- www.ubuntu.com
- security.gentoo.org
- www.exploit-db.com
- www.imagemagick.org
- www.cisa.gov
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-3715 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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