# CVE-2010-0299: openSUSE 11.2 installs the devtmpfs root directory with insecure permissions (1777), which allows local users to gain privileges via unspecified vectors.


- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rwvq-hc2g-qj75

## What is CVE-2010-0299?

CVE-2010-0299 is a medium-severity vulnerability in Opensuse Opensuse, published on 22 Feb 2010. 

### Official description

openSUSE 11.2 installs the devtmpfs root directory with insecure permissions (1777), which allows local users to gain privileges via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Opensuse Opensuse.

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

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

## Is CVE-2010-0299 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2015-5957](https://insights.sbomify.com/CVE-2015-5957/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-0491](https://insights.sbomify.com/CVE-2015-0491/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-2388](https://insights.sbomify.com/CVE-2008-2388/): Integer overflow in n/a (critical 10.0)
- [CVE-2010-1866](https://insights.sbomify.com/CVE-2010-1866/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-0492](https://insights.sbomify.com/CVE-2015-0492/): Other in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0299 is a medium-severity vulnerability in Opensuse Opensuse, published on 22 Feb 2010. 
Exploitation: There is no known exploitation of CVE-2010-0299 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-0299/ (Markdown: https://insights.sbomify.com/CVE-2010-0299/index.md)
```

## Sources

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

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