# CVE-2004-1388: Memory corruption in n/a

> Remote attackers can execute arbitrary code via format string vulnerabilities in the gpsd daemon's syslog reporting function.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** CVE-2005-0228, DEBIAN-CVE-2004-1388, GHSA-6g3h-vj3c-7f68

## What is CVE-2004-1388?

CVE-2004-1388 is a high-severity memory corruption vulnerability in n/a, published on 6 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in the gpsd_report function for BerliOS GPD daemon (gpsd, formerly pygps) 1.9.0 through 2.7 allows remote attackers to execute arbitrary code via certain GPS requests containing format string specifiers that are not properly handled in syslog calls.

## Which versions are affected by CVE-2004-1388?

It affects 1 product.


Products: Berlios Gps Daemon.

## How do I fix CVE-2004-1388?

Upgrade to a fixed version.

## Is CVE-2004-1388 being exploited?

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

Public exploit code:

- Berlios GPSD 2.7.x - Remote Format String (exploitdb)
- Berlios GPSD 1.91-1 < 2.7-2 - Format String (exploitdb)
- Berlios GPSD Format String Vulnerability (metasploit)
- Berlios GPSD 2.7 - Remote Format String (Metasploit) (exploitdb)
- Berlios GPSD - Format String (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1388 and fix it if it is affected.

What it is: CVE-2004-1388 is a high-severity memory corruption vulnerability in n/a, published on 6 Feb 2005. 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-2004-1388 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-2004-1388/ (Markdown: https://insights.sbomify.com/CVE-2004-1388/index.md)
```

## Sources

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

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