# CVE-2008-3024: Memory corruption in n/a

> Local attackers can gain privileges via a stack-based buffer overflow in phgrafx triggered by a long .pal filename.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5vh8-vx9c-m2vw

## What is CVE-2008-3024?

CVE-2008-3024 is a critical memory corruption vulnerability in n/a, published on 7 Jul 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based buffer overflow in phgrafx in QNX Momentics (aka RTOS) 6.3.2 and earlier allows local users to gain privileges via a long .pal filename in palette/.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2008-3024?

It affects 1 product.


Products: Blackberry Qnx Momentics.

## How do I fix CVE-2008-3024?

No fix has been published for CVE-2008-3024 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-3024 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-3024 exists.

Public exploit code:

- QNX Neutrino RTOS 6.3 - 'phgrafx' Local Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-32025](https://insights.sbomify.com/CVE-2021-32025/): Privilege escalation in QNX Software Development Platform (SDP), QNX OS for Medical (QOSM), and QNX OS for Safety (QOS) (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3024 and fix it if it is affected.

What it is: CVE-2008-3024 is a critical memory corruption vulnerability in n/a, published on 7 Jul 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-3024 exists.

Affected product: n/a. 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-2008-3024/ (Markdown: https://insights.sbomify.com/CVE-2008-3024/index.md)
```

## Sources

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

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