# CVE-2007-0475: Memory corruption in n/a

> Local users on the Smb4K sudoers list can exploit stack-based buffer overflows to gain elevated privileges.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-0475, GHSA-37jj-mf3j-h43w

## What is CVE-2007-0475?

CVE-2007-0475 is a medium-severity memory corruption vulnerability in n/a, published on 3 Feb 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in utilities/smb4k_*.cpp in Smb4K before 0.8.0 allow local users, when present on the Smb4K sudoers list, to gain privileges via unspecified vectors related to the args variable and unspecified other variables, in conjunction with the sudo configuration.

## Which versions are affected by CVE-2007-0475?

It affects 1 product.


Products: Smb4k Smb4k.

## How do I fix CVE-2007-0475?

Upgrade to a fixed version.

## Is CVE-2007-0475 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0472](https://insights.sbomify.com/CVE-2007-0472/): Race condition in n/a (low 3.7)
- [CVE-2007-0474](https://insights.sbomify.com/CVE-2007-0474/): Privilege escalation in n/a (low 3.3)
- [CVE-2005-2851](https://insights.sbomify.com/CVE-2005-2851/): Path traversal in n/a (low 2.1)
- [CVE-2007-0473](https://insights.sbomify.com/CVE-2007-0473/): Information disclosure in n/a (low 1.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0475 and fix it if it is affected.

What it is: CVE-2007-0475 is a medium-severity memory corruption vulnerability in n/a, published on 3 Feb 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0475 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-2007-0475/ (Markdown: https://insights.sbomify.com/CVE-2007-0475/index.md)
```

## Sources

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

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