# CVE-2013-2069: Missing authorization in n/a

> Local attackers can gain root privileges if the Kickstart file lacks a root password directive, affecting Red Hat livecd-tools.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2013
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2013-2084, GHSA-7pfq-gm79-4p7f

## What is CVE-2013-2069?

CVE-2013-2069 is a high-severity missing authorization vulnerability in n/a, published on 29 May 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Red Hat livecd-tools before 13.4.4, 17.x before 17.17, 18.x before 18.16, and 19.x before 19.3, when a rootpw directive is not set in a Kickstart file, sets the root user password to empty, which allows local users to gain privileges.

Weakness: CWE-264

## Which versions are affected by CVE-2013-2069?

It affects 1 product.


Products: Redhat Livecd-Tools.

## How do I fix CVE-2013-2069?

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

## Is CVE-2013-2069 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2069 and fix it if it is affected.

What it is: CVE-2013-2069 is a high-severity missing authorization vulnerability in n/a, published on 29 May 2013. 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-2013-2069 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-2013-2069/ (Markdown: https://insights.sbomify.com/CVE-2013-2069/index.md)
```

## Sources

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

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