dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
Enterprise Linux DesktopOperating system · Redhat

CVE-2016-3718

MEDIUM · 5.5 CVSS v3.1 Published 2016-05-05
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
97/100
Remediation priority · Urgent
In the wild High EPSS Public exploit No privileges Patch available

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
The (1) HTTP and (2) FTP coders in ImageMagick before 6.9.3-10 and 7.x before 7.0.1-1 allow remote attackers to conduct server-side request forgery (SSRF) attacks 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 · moderate confidence

The HTTP and FTP coders in ImageMagick versions prior to 6.9.3-10 and 7.x prior to 7.0.1-1 contain a server-side request forgery (SSRF) vulnerability. Attackers can embed malicious URLs within crafted image files that, when processed by ImageMagick, cause the server to make arbitrary HTTP or FTP requests to attacker-controlled or internal resources.

MitigationUpgrade ImageMagick to version 6.9.3-10/7.0.1-1 or later; alternatively, disable the HTTP and FTP coders in ImageMagick's policy.xml configuration file to prevent URL handling.

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
Enterprise Linux DesktopOperating system
Affected:= 6.0= 7.0
Enterprise Linux EusOperating system
Affected:= 6.7= 7.2= 7.3= 7.4= 7.5= 7.6= 7.7
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 6.0_s390x= 7.0_s390x
Enterprise Linux For Ibm Z Systems EusOperating system
Affected:= 6.7_s390x= 7.2_s390x= 7.3_s390x= 7.4_s390x= 7.5_s390x= 7.6_s390x= 7.7_s390x
Enterprise Linux For Power Big EndianOperating system
Affected:= 6.0_ppc64= 7.0_ppc64
Enterprise Linux For Power Big Endian EusOperating system
Affected:= 6.7_ppc64= 7.2_ppc64= 7.3_ppc64= 7.4_ppc64= 7.5_ppc64= 7.6_ppc64= 7.7_ppc64
Enterprise Linux For Power Little EndianOperating system
Affected:= 7.0_ppc64le
Enterprise Linux For Power Little Endian EusOperating system
Affected:= 7.2_ppc64le= 7.3_ppc64le= 7.4_ppc64le= 7.5_ppc64le= 7.6_ppc64le= 7.7_ppc64le

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
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 checks

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

  1. Check if ImageMagick is installed
    Run `rpm -qa | grep -i ImageMagick` on RHEL-based systems, or check for the `identify`, `convert`, or `magick` commands using `which identify`
    Affected if ImageMagick is not installed on the system, the vulnerability does not apply
  2. Determine the installed ImageMagick version
    Run `rpm -q --queryformat '%{VERSION}' ImageMagick` or `convert -version` and look at the version number in the output
    Affected if The installed version is before 6.9.3-10 (for the 6.x branch) or before 7.0.1-1 (for the 7.x branch), and the system matches the affected RHEL versions listed in the CVE
  3. Check if HTTP/FTP coders are enabled in ImageMagick policy
    Inspect the policy configuration file at `/etc/ImageMagick/policy.xml` and look for <coder> entries that restrict or disable 'http' or 'ftp' protocols
    Affected if The HTTP and FTP coders are not explicitly restricted or disabled, meaning the application can still make arbitrary HTTP/FTP requests
  4. Verify the ImageMagick policy file location and contents
    Run `convert -list configure | grep POLICY_PATH` to find the policy file location, then `cat` that file to inspect restrictions
    Affected if No policy restrictions exist for HTTP/FTP coders, leaving the SSRF attack vector open

The system is affected if ImageMagick is installed with a version before 6.9.3-10 (6.x branch) or before 7.0.1-1 (7.x branch) on a vulnerable RHEL version, AND the HTTP/FTP coders are not disabled in the policy configuration.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch git.imagemagick.org →
Interim mitigation

Upgrade ImageMagick to version 6.9.3-10/7.0.1-1 or later; alternatively, disable the HTTP and FTP coders in ImageMagick's policy.xml configuration file to prevent URL handling.

Recommended fix High confidence

ImageMagick 6.9.3-10 or later, or ImageMagick 7.0.1-1 or later

  1. Update the ImageMagick packages by running 'yum update ImageMagick' or 'dnf update ImageMagick' on the affected system
  2. After updating, verify the installed version matches or exceeds 6.9.3-10 (for ImageMagick 6.x) or 7.0.1-1 (for ImageMagick 7.x) using 'rpm -q ImageMagick' or 'magick --version'
  3. Restart any services that use ImageMagick to ensure the patched version is loaded
  4. Optionally, review /etc/ImageMagick/policy.xml to restrict remote resource access (if the upgrade is not immediately possible)
Caveat Standard upgrade; minor configuration adjustments may be needed if custom ImageMagick policies are in place

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Linux Desktop Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get it fixed fast

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-2016-3718 — 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-2016-3718 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