CVE-2013-1060 json
A certain Ubuntu build procedure for perf, as distributed in the Linux kernel packages in Ubuntu 10.04 LTS, 12.04 LTS, 12.10, 13.04, and 13…
published 13y ago modified 4mo ago also EUVD-2013-1100
- cvss
- 6.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
A certain Ubuntu build procedure for perf, as distributed in the Linux kernel packages in Ubuntu 10.04 LTS, 12.04 LTS, 12.10, 13.04, and 13.10, sets the HOME environment variable to the ~buildd directory and consequently reads the system configuration file from the ~buildd directory, which allows local users to gain privileges by leveraging control over the buildd account.
Is CVE-2013-1060 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
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.9 | AV:L/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
ubuntu.com
/usn/USN-1943-1
vendor-advisory
-
ubuntu.com
/usn/USN-1938-1
vendor-advisory
-
ubuntu.com
/usn/USN-1944-1
vendor-advisory
-
ubuntu.com
/usn/USN-1945-1
vendor-advisory
-
ubuntu.com
/usn/USN-1939-1
vendor-advisory
-
ubuntu.com
/usn/USN-1947-1
vendor-advisory
-
ubuntu.com
/usn/USN-1941-1
vendor-advisory
-
ubuntu.com
/usn/USN-1942-1
vendor-advisory
-
ubuntu.com
/usn/USN-1946-1
vendor-advisory
-
people.canonical.com
/~ubuntu-security/cve/2013/CVE-2013-1060.html
vendor-advisory
- launchpad.net /bugs/1206200
-
lists.ubuntu.com
/archives/kernel-team/2013-July/031248.html
mailing-list
-
lists.ubuntu.com
/archives/kernel-team/2013-July/031249.html
mailing-list
Sources
- CVE List CVE-2013-1060
- NVD CVE-2013-1060
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.