# CVE-2005-3995: Memory corruption in n/a

> Remote attackers can execute arbitrary code via format string vulnerabilities in OBEX file name arguments when syslog is enabled.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 5 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mhxv-2pvp-28fg

## What is CVE-2005-3995?

CVE-2005-3995 is a medium-severity memory corruption vulnerability in n/a, published on 5 Dec 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 dosyslog function in the OBEX server (obexsrv.c) for Sobexsrv before 1.0.0-pre4, when the syslog (-S) function is enabled, allows remote attackers to execute arbitrary code via format string specifiers in file name arguments to OBEX commands.

## Which versions are affected by CVE-2005-3995?

It affects 1 product.


Products: Sobexsrv Sobexsrv.

## How do I fix CVE-2005-3995?

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

## Is CVE-2005-3995 being exploited?

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

Public exploit code:

- sobexsrv 1.0.0_pre3 Bluetooth - 'syslog()' Remote Format String (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3995 and fix it if it is affected.

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

## Sources

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

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