# CVE-2009-1364: Use after free in n/a

> A use-after-free flaw in libwmf allows attackers to execute arbitrary code or crash applications via crafted WMF files.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1364, DSA-1796-1, GHSA-6h8h-vx9v-4g94, RHSA-2009:0457

## What is CVE-2009-1364?

CVE-2009-1364 is a high-severity use after free vulnerability in Opensuse Opensuse, published on 1 May 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Use-after-free vulnerability in the embedded GD library in libwmf 0.2.8.4 allows context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted WMF file.

## Which versions are affected by CVE-2009-1364?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libwmf` | Red Hat:enterprise_linux:4::as | All versions | 0:0.2.8.3-5.8 |
| `libwmf-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:0.2.8.3-5.8 |
| `libwmf-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:0.2.8.3-5.8 |
| `libwmf` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.2.8.3-5.8 |
| `libwmf-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.2.8.3-5.8 |
| `libwmf-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.2.8.3-5.8 |
| `libwmf` | Red Hat:enterprise_linux:4::es | All versions | 0:0.2.8.3-5.8 |
| `libwmf-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:0.2.8.3-5.8 |
| `libwmf-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:0.2.8.3-5.8 |
| `libwmf` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.2.8.3-5.8 |
| `libwmf-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.2.8.3-5.8 |
| `libwmf-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.2.8.3-5.8 |
| `libwmf` | Red Hat:enterprise_linux:5::client | All versions | 0:0.2.8.4-10.2 |
| `libwmf-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:0.2.8.4-10.2 |
| `libwmf` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:0.2.8.4-10.2 |
| `libwmf-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:0.2.8.4-10.2 |
| `libwmf-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:0.2.8.4-10.2 |
| `libwmf` | Red Hat:enterprise_linux:5::server | All versions | 0:0.2.8.4-10.2 |
| `libwmf-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:0.2.8.4-10.2 |
| `libwmf-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:0.2.8.4-10.2 |

Products: Francis James Franklin Libwmf, Opensuse Opensuse.

## How do I fix CVE-2009-1364?

Apply the vendor's patch.

## Is CVE-2009-1364 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1364 and fix it if it is affected.

What it is: CVE-2009-1364 is a high-severity use after free vulnerability in Opensuse Opensuse, published on 1 May 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-1364 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-2009-1364/ (Markdown: https://insights.sbomify.com/CVE-2009-1364/index.md)
```

## Sources

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

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