# CVE-2018-1000222: Use after free in n/a

> A double free vulnerability in Libgd allows remote code execution via a specially crafted JPEG image.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-1000222, DEBIAN-CVE-2018-1000222, GHSA-jcj9-h5mg-pr5c, SUSE-SU-2018:2837-1, SUSE-SU-2018:2840-1, SUSE-SU-2018:2888-1, UBUNTU-CVE-2018-1000222

## What is CVE-2018-1000222?

CVE-2018-1000222 is a high-severity use after free vulnerability in Canonical Ubuntu Linux, published on 20 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2018-1000222?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gd` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 2.1.0-24.9.1 |
| `gd` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 2.2.5-4.3.1 |
| `gd` | SUSE:Linux Enterprise Module for Desktop Applications 15 | All versions | 2.2.5-4.3.1 |
| `php7` | SUSE:Linux Enterprise Module for Web and Scripting 15 | All versions | 7.2.5-4.9.1 |
| `gd` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 2.1.0-24.9.1 |
| `gd` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2.1.0-24.9.1 |
| `gd` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 2.1.0-24.9.1 |
| `gd` | SUSE:Linux Enterprise Workstation Extension 12 SP3 | All versions | 2.1.0-24.9.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Libgd Libgd.

## How do I fix CVE-2018-1000222?

Apply the vendor's patch.

## Is CVE-2018-1000222 being exploited?

There is no known exploitation of CVE-2018-1000222 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000222 and fix it if it is affected.

What it is: CVE-2018-1000222 is a high-severity use after free vulnerability in Canonical Ubuntu Linux, published on 20 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1000222 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1000222/ (Markdown: https://insights.sbomify.com/CVE-2018-1000222/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1000222
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1000222
- OSV: https://osv.dev/vulnerability/CVE-2018-1000222

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1000222/
Summaries are generated and may contain mistakes; the official description above is the record.