# CVE-2008-0764: Other in n/a

> Remote attackers can execute arbitrary code via format string vulnerabilities in the Larson Network Print Server logging function.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5g4w-m5hx-7hw6

## What is CVE-2008-0764?

CVE-2008-0764 is a critical vulnerability in n/a, published on 13 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Format string vulnerability in the logging function in Larson Network Print Server (LstNPS) 9.4.2 build 105 and earlier for Windows might allow remote attackers to execute arbitrary code via format string specifiers in a USEP command on TCP port 3114.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Larson Software Technology Network Print Server.

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

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

## Is CVE-2008-0764 being exploited?

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

Public exploit code:

- Larson Network Print Server 9.4.2 build 105 - 'LstNPS' Logging Function USEP Command Remote Format String (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-0763](https://insights.sbomify.com/CVE-2008-0763/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0764 is a critical vulnerability in n/a, published on 13 Feb 2008. 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-2008-0764 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-0764/ (Markdown: https://insights.sbomify.com/CVE-2008-0764/index.md)
```

## Sources

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

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