# CVE-2013-1064: Race condition in n/a

> Local attackers can exploit a race condition in apt-xapian-index to bypass access restrictions and escalate privileges via Polkit.

- **Severity:** Medium 4.6 (`AV:L/AC:L/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 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2013-1064, GHSA-f46w-pmxr-fvq6

## What is CVE-2013-1064?

CVE-2013-1064 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 3 Oct 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

apt-xapian-index before 0.45ubuntu2.1, 0.44ubuntu7.1, and 0.44ubuntu5.1 does not properly use D-Bus for communication with a polkit authority, which allows local users to bypass intended access restrictions by leveraging a PolkitUnixProcess PolkitSubject race condition via a (1) setuid process or (2) pkexec process, a related issue to CVE-2013-4288.

Weakness: CWE-264

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

It affects 2 products.


Products: Canonical Apt-Xapian-Index, Canonical Ubuntu Linux.

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

Upgrade to a fixed version.

## Is CVE-2013-1064 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1064 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 3 Oct 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-1064 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-1064/ (Markdown: https://insights.sbomify.com/CVE-2013-1064/index.md)
```

## Sources

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

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