CVE-2022-47952

NameCVE-2022-47952
Descriptionlxc-user-nic in lxc through 5.0.1 is installed setuid root, and may allow local users to infer whether any file exists, even within a protected directory tree, because "Failed to open" often indicates that a file does not exist, whereas "does not refer to a network namespace path" often indicates that a file exists. NOTE: this is different from CVE-2018-6556 because the CVE-2018-6556 fix design was based on the premise that "we will report back to the user that the open() failed but the user has no way of knowing why it failed"; however, in many realistic cases, there are no plausible reasons for failing except that the file does not exist.
SourceCVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
ReferencesDLA-3533-1

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
lxc (PTS)jessie, jessie (lts)1:1.0.6-6+deb8u6vulnerable
stretch1:2.0.7-2+deb9u2fixed
buster (security), buster, buster (lts)1:3.1.0+really3.0.3-8+deb10u1fixed
bullseye1:4.0.6-2+deb11u2fixed
bookworm1:5.0.2-1+deb12u2fixed
sid, trixie1:6.0.2-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
lxcsourcejessie(unfixed)end-of-life
lxcsourcestretch(not affected)
lxcsourcebuster1:3.1.0+really3.0.3-8+deb10u1DLA-3533-1
lxcsourcebullseye1:4.0.6-2+deb11u2
lxcsource(unstable)1:5.0.2-1

Notes

https://bugzilla.redhat.com/show_bug.cgi?id=2157281
https://github.com/MaherAzzouzi/CVE-2022-47952
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1783591/comments/45
Different issue than CVE-2018-6556
https://github.com/lxc/lxc/commit/80553b5b412365f429aff93cff178e3e952ee6bd
[stretch] - lxc <not-affected> (The vulnerable code was introduced later. Reproducer no-op)

Search for package or bug name: Reporting problems