# CVE-2003-1359: Memory corruption in n/a

> Local attackers can exploit a buffer overflow in the stmkfont utility to gain elevated privileges on HP-UX systems.

- **Severity:** High 7.2 (`AV:L/AC:L/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:** 17 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5657-h9cj-f78j

## What is CVE-2003-1359?

CVE-2003-1359 is a high-severity memory corruption vulnerability in Hp Hp-Ux, published on 17 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in stmkfont utility of HP-UX 10.0 through 11.22 allows local users to gain privileges via a long command line argument.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2003-1359?

It affects 2 products.


Products: Avaya Predictive Dialer System, Hp Hp-Ux.

## How do I fix CVE-2003-1359?

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

## Is CVE-2003-1359 being exploited?

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

Public exploit code:

- HP-UX 10.x - stmkfont Alternate Typeface Library Buffer Overflow (1) (exploitdb)
- HP-UX 10.x - stmkfont Alternate Typeface Library Buffer Overflow (2) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1359 and fix it if it is affected.

What it is: CVE-2003-1359 is a high-severity memory corruption vulnerability in Hp Hp-Ux, published on 17 Oct 2007. 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-2003-1359 exists.

Affected product: Hp Hp-Ux. 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-2003-1359/ (Markdown: https://insights.sbomify.com/CVE-2003-1359/index.md)
```

## Sources

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

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