# CVE-2007-4206: Privilege escalation in n/a

> Local attackers can exploit incorrect file permissions during upgrades to gain elevated privileges on systems running Kaspersky Anti-Spam.

- **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:** No
- **Published:** 8 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7ghr-4c3p-5m65

## What is CVE-2007-4206?

CVE-2007-4206 is a medium-severity vulnerability in n/a, published on 8 Aug 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kaspersky Anti-Spam 3.0 MP1 before Critical Fix 2 (3.0.278.4) sets incorrect permissions for application files in certain upgrade scenarios, which might allow local users to gain privileges.

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

It affects 1 product.


Products: Kaspersky Lab Kaspersky Anti-Spam.

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

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

## Is CVE-2007-4206 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3502](https://insights.sbomify.com/CVE-2007-3502/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4206 is a medium-severity vulnerability in n/a, published on 8 Aug 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-4206 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-4206/ (Markdown: https://insights.sbomify.com/CVE-2007-4206/index.md)
```

## Sources

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

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