Skip to content
Fencer Intel
medium 4.9

CVE-2015-1331 json

lxclock.c in LXC 1.1.2 and earlier allows local users to create arbitrary files via a symlink attack on /run/lock/lxc/*.

published 11y ago modified 4mo ago also EUVD-2015-1471

cvss
4.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

lxclock.c in LXC 1.1.2 and earlier allows local users to create arbitrary files via a symlink attack on /run/lock/lxc/*.

Patch / fix

  • lxc Debian 14, Debian 13, Debian 12 1:1.0.7-4

debian advisories DEBIAN-CVE-2015-1331

  • lxc Ubuntu 14.04 LTS 1.0.7-0ubuntu0.2

ubuntu advisories UBUNTU-CVE-2015-1331

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

  • lxc openSUSE Tumbleweed 2.0.4-2.1

opensuse advisories openSUSE-SU-2024:10416-1

Is CVE-2015-1331 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 Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-1331 updated cvss 2.6

lxc: directory traversal flaw

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugs.launchpad.net https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470842 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.9 AV:L/AC:L/Au:N/C:N/I:C/A:N

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

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.