CVE-2013-1068 json
The OpenStack Nova (python-nova) package 1:2013.2.3-0 before 1:2013.2.3-0ubuntu1.2 and 1:2014.1-0 before 1:2014.1-0ubuntu1.2 and Openstack…
published 12y ago modified 4mo ago also EUVD-2013-1108
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
The OpenStack Nova (python-nova) package 1:2013.2.3-0 before 1:2013.2.3-0ubuntu1.2 and 1:2014.1-0 before 1:2014.1-0ubuntu1.2 and Openstack Cinder (python-cinder) package 1:2013.2.3-0 before 1:2013.2.3-0ubuntu1.1 and 1:2014.1-0 before 1:2014.1-0ubuntu1.1 for Ubuntu 13.10 and 14.04 LTS does not properly set the sudo configuration, which makes it easier for attackers to gain privileges by leveraging another vulnerability.
Patch / fix
- nova Debian 14, Debian 13, Debian 12 2014.1.1-4
- cinder Debian 14, Debian 13, Debian 12 2014.1.1-3
debian advisories DEBIAN-CVE-2013-1068
- nova Ubuntu 14.04 LTS 1:2014.1-0ubuntu1.2
- cinder Ubuntu 14.04 LTS 1:2014.1-0ubuntu1.1
ubuntu advisories UBUNTU-CVE-2013-1068
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- ubuntu.com/usn/usn-2248-1 advisory
- ubuntu.com/usn/USN-2247-1 advisory
Is CVE-2013-1068 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
ubuntu.com
/usn/usn-2248-1
vendor-advisory, patch
-
ubuntu.com
/usn/USN-2247-1
vendor-advisory, patch
Sources
- CVE List CVE-2013-1068
- NVD CVE-2013-1068
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.