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

> Remote attackers can execute arbitrary code via format string vulnerabilities in IBM solidDB logging functions without authentication.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 9 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pm8g-j2pp-65h6

## What is CVE-2008-1705?

CVE-2008-1705 is a medium-severity vulnerability in n/a, published on 9 Apr 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 IBM solidDB 06.00.1018 and earlier allows remote attackers to execute arbitrary code via format string specifiers in the (1) user name, (2) peer name, and possibly unspecified other fields.

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

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

It affects 1 product.


Products: Ibm Soliddb.

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

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

## Is CVE-2008-1705 being exploited?

There is no known exploitation of CVE-2008-1705 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2010-2771](https://insights.sbomify.com/CVE-2010-2771/): Code injection in n/a (critical 10.0)
- [CVE-2011-1560](https://insights.sbomify.com/CVE-2011-1560/): Auth bypass in n/a (critical 9.3)
- [CVE-2011-1208](https://insights.sbomify.com/CVE-2011-1208/): Null dereference in n/a (high 7.8)
- [CVE-2010-4055](https://insights.sbomify.com/CVE-2010-4055/): Denial of service in n/a (medium 5.0)
- [CVE-2010-4056](https://insights.sbomify.com/CVE-2010-4056/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1705 is a medium-severity vulnerability in n/a, published on 9 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-1705 in the wild and no public exploit code.

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-1705/ (Markdown: https://insights.sbomify.com/CVE-2008-1705/index.md)
```

## Sources

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

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