Bug 2157281 (CVE-2022-47952) - CVE-2022-47952 lxc: information disclosure vulnerability
Summary: CVE-2022-47952 lxc: information disclosure vulnerability
Alias: CVE-2022-47952
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 2157282 2157283
TreeView+ depends on / blocked
Reported: 2023-01-01 16:28 UTC by ybuenos
Modified: 2023-01-03 03:30 UTC (History)
0 users

Fixed In Version:
Doc Type: ---
Doc Text:
An information disclosure vulnerability was found in lxc up to 5.0.1. Local users may be able to infer whether any file exists, even within a protected directory tree, via the application's generation of a "Failed to open" error message.
Clone Of:
Last Closed: 2023-01-03 03:30:38 UTC

Attachments (Terms of Use)

Description ybuenos 2023-01-01 16:28:30 UTC
lxc-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.


Comment 1 ybuenos 2023-01-01 16:28:46 UTC
Created lxc tracking bugs for this issue:

Affects: epel-all [bug 2157282]
Affects: fedora-all [bug 2157283]

Comment 2 Product Security DevOps Team 2023-01-03 03:30:36 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.

Note You need to log in before you can comment on or make changes to this bug.