# CVE-2003-0625: Information disclosure in n/a

> Remote attackers can read sensitive memory from the XFS font server via a malformed handshake request due to an off-by-one error.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Aug 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0625, GHSA-774m-fhgf-hrhc

## What is CVE-2003-0625?

CVE-2003-0625 is a high-severity vulnerability in n/a, published on 1 Aug 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Off-by-one error in certain versions of xfstt allows remote attackers to read potentially sensitive memory via a malformed client request in the connection handshake, which leaks the memory in the server's response.

Weakness: CWE-193 (Off-by-one Error)

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

It affects 1 product.


Products: Hadrons Xfstt.

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

Apply the vendor's patch.

## Is CVE-2003-0625 being exploited?

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

Public exploit code:

- xfstt 1.2/1.4 - Memory Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0625 is a high-severity vulnerability in n/a, published on 1 Aug 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0625 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-2003-0625/ (Markdown: https://insights.sbomify.com/CVE-2003-0625/index.md)
```

## Sources

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

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