dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2018-1000222

HIGH · 8.8 CVSS v3.0 Published 2018-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
Libgd version 2.2.5 contains a Double Free Vulnerability vulnerability in gdImageBmpPtr Function that can result in Remote Code Execution . This attack appear to be exploitable via Specially Crafted Jpeg Image can trigger double free. This vulnerability appears to have been fixed in after commit ac16bdf2d41724b5a65255d4c28fb0ec46bc42f5.

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

Libgd 2.2.5 contains a double-free vulnerability in the gdImageBmpPtr function that can be triggered by a specially crafted JPEG/BMP image, potentially allowing remote code execution.

MitigationUpdate libgd to a version after commit ac16bdf2d41724b5a65255d4c28fb0ec46bc42f5, or apply the specific patch from that commit to fix the double-free in gdImageBmpPtr.

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= 18.04
Debian LinuxOperating system
Affected:= 8.0
LibgdApplication
Affected:= 2.2.5

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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. Identify installed libgd version
    Run 'dpkg -l | grep libgd' on Debian/Ubuntu, or 'rpm -qa | grep gd' on RHEL-based systems, or check '/usr/lib/x86_64-linux-gnu/libgd.so.3' (or similar path) and run 'ldd' on it
    Affected if The version shown is 2.2.5 exactly, or if the package version matches the listed vulnerable releases (Ubuntu 14.04, 16.04, 18.04 or Debian 8.0)
  2. Locate libgd library file
    Run 'find /usr -name "libgd*" -type f 2>/dev/null' to find libgd shared objects, then use 'strings' or check package metadata for version info
    Affected if The library file present is version 2.2.5 or comes from the vulnerable Ubuntu/Debian releases listed
  3. Identify applications using gdImageBmpPtr
    Search application source code for calls to 'gdImageBmpPtr' using 'grep -r "gdImageBmpPtr" /path/to/code', or use 'nm -D' on compiled binaries to list imported symbols
    Affected if The application links against libgd and calls the gdImageBmpPtr function to process BMP or JPEG images
  4. Confirm image processing capability
    Check if the application or service processes BMP or JPEG files by reviewing configuration, uploaded file handlers, or runtime logs showing image format acceptance
    Affected if The environment accepts or processes BMP or JPEG image uploads or transformations using libgd

You are affected if libgd version 2.2.5 (or the vulnerable Ubuntu/Debian package versions) is installed AND applications use gdImageBmpPtr to process BMP or JPEG images.

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 libgd to a version after commit ac16bdf2d41724b5a65255d4c28fb0ec46bc42f5, or apply the specific patch from that commit to fix the double-free in gdImageBmpPtr.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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