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

> Remote attackers can execute arbitrary code via format string vulnerabilities in the LPD server queue name handling.

- **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:** No
- **Published:** 13 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rc66-4982-rv68

## What is CVE-2008-0755?

CVE-2008-0755 is a high-severity 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 ReportSysLogEvent function in the LPD server in cyan soft Opium OPI Server 4.10.1028 and earlier; cyanPrintIP Easy OPI, Professional, and Basic 4.10.1030 and earlier; Workstation 4.10.836 and earlier; and Standard 4.10.940 and earlier; might allow remote attackers to execute arbitrary code via format string specifiers in the queue name in a request.

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

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

It affects 6 products.


Products: Cyan Soft Cyanprintip Basic, Cyan Soft Cyanprintip Easy Opi, Cyan Soft Cyanprintip Professional, Cyan Soft Cyanprintip Standard, Cyan Soft Cyanprintip Workstation, Cyan Soft Opium4 Opi Server.

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

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

## Is CVE-2008-0755 being exploited?

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

Public exploit code:

- Opium OPI Server and CyanPrintIP - Format String / Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-0756](https://insights.sbomify.com/CVE-2008-0756/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0755 is a high-severity 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-0755 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-0755/ (Markdown: https://insights.sbomify.com/CVE-2008-0755/index.md)
```

## Sources

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

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