# CVE-2010-4512: Misconfiguration in n/a

> Local attackers can read or modify sensitive files due to insecure default permissions in Cobbler.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 9 Dec 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qpw7-wxj3-c3xw

## What is CVE-2010-4512?

CVE-2010-4512 is a high-severity vulnerability in n/a, published on 9 Dec 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cobbler before 2.0.4 uses an incorrect umask value, which allows local users to have an unspecified impact by leveraging world writable permissions for files and directories.

Weakness: CWE-264

## Which versions are affected by CVE-2010-4512?

It affects 1 product.


Products: Michael Dehaan Cobbler.

## How do I fix CVE-2010-4512?

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

## Is CVE-2010-4512 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-6954](https://insights.sbomify.com/CVE-2008-6954/): Cobbler Web Interface Kickstart Template Remote Privilege Escalation Vulnerability (critical 9.0)
- [CVE-2010-2235](https://insights.sbomify.com/CVE-2010-2235/): Cobbler is vulnerable to code injection (high 8.5)
- [CVE-2012-2395](https://insights.sbomify.com/CVE-2012-2395/): Cobbler subject to Command Injection (high 7.5)
- [CVE-2009-5021](https://insights.sbomify.com/CVE-2009-5021/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4512 and fix it if it is affected.

What it is: CVE-2010-4512 is a high-severity vulnerability in n/a, published on 9 Dec 2010. 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-2010-4512 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-2010-4512/ (Markdown: https://insights.sbomify.com/CVE-2010-4512/index.md)
```

## Sources

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

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