dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2017-17934

MEDIUM · 6.5 CVSS v3.0 Published 2017-12-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
ImageMagick 7.0.7-17 Q16 x86_64 has memory leaks in coders/msl.c, related to MSLPopImage and ProcessMSLScript, and associated with mishandling of MSLPushImage calls.

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

ImageMagick 7.0.7-17 contains a memory leak vulnerability in coders/msl.c. The issue occurs in the MSLPopImage and ProcessMSLScript functions due to improper handling of MSLPushImage calls, leading to memory not being properly freed during MSL (Magick Scripting Language) script processing.

MitigationUpdate to a patched version of ImageMagick that fixes the memory leak in coders/msl.c. If immediate patching is not possible, disable or restrict MSL script processing as a temporary workaround.

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
Ubuntu LinuxOperating system
Affected:= 14.04= 16.04= 17.10= 18.04
ImagemagickApplication
Affected:= 7.0.7-17

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 ImageMagick version
    Run 'convert --version' or 'identify --version' to see the installed ImageMagick version number
    Affected if The version shown is exactly 7.0.7-17 (or falls within the 7.0.7-17 range)
  2. Verify MSL coder module availability
    Check if the MSL (Magick Scripting Language) coder is available by examining the ImageMagick configuration or running 'convert -list configure' to see compiled-in coders
    Affected if The MSL coder module is present and loadable in the ImageMagick installation
  3. Confirm MSL script processing is in use
    Look for any .msl script files in your environment, or check application logs/usage for processes that invoke ImageMagick with MSL scripts using the 'msl:' delegate
    Affected if Your environment processes or has recently processed MSL scripts (files using the .msl extension or msL: protocol)
  4. Check for MSL delegate configuration
    Review ImageMagick's policy.xml or delegate configuration files to see if MSL script handling is enabled (look for 'msl' entries in delegates.xml)
    Affected if MSL delegate is configured and enabled in ImageMagick's delegate/delegation settings

You are affected if ImageMagick version 7.0.7-17 is installed AND the MSL coder/delegate is present AND your environment processes MSL scripts

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of ImageMagick that fixes the memory leak in coders/msl.c. If immediate patching is not possible, disable or restrict MSL script processing as a temporary workaround.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-17934 — 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-17934 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