{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-47952 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-47952 is a low-severity vulnerability in n/a, published on 1 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-47952 and fix it if it is affected.\n\nWhat it is: CVE-2022-47952 is a low-severity vulnerability in n/a, published on 1 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-47952 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-47952/ (Markdown: https://insights.sbomify.com/CVE-2022-47952/index.md)","id":"CVE-2022-47952","markdown":"https://insights.sbomify.com/CVE-2022-47952/index.md","name":"CVE-2022-47952","record":{"aliases":["ALPINE-CVE-2022-47952","DEBIAN-CVE-2022-47952","DLA-3533-1","GHSA-qv29-rjwj-jjrm","OESA-2023-1075","OESA-2023-1076","OESA-2023-1077","UBUNTU-CVE-2022-47952","openSUSE-SU-2024:0342-1","openSUSE-SU-2024:12935-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux container runtime","requires_auth":"low_privilege","summary":"Local attackers can infer file existence in protected directories via error message differences in the setuid lxc-user-nic binary.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lxc","vendor":"linuxcontainers"}],"cvss":{"score":3.3,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"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.","ecosystems":["SUSE:Package Hub 15 SP5","SUSE:Package Hub 15 SP6","openSUSE:Leap 15.5","openSUSE:Leap 15.6","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":"2022-12-31","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-12-31T21:24:46Z","kind":"github_poc","ref":"https://github.com/MaherAzzouzi/CVE-2022-47952","stars":0,"title":"LXC Information Disclosure vulnerability."}],"tier":"poc_unverified"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2022-47952","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":5,"n_references":5,"next":{"headline":"Memory corruption in macOS","id":"CVE-2022-47965"},"packages":[{"ecosystem":"SUSE:Package Hub 15 SP5","fixed":["6.0.2-bp156.2.3.1"],"introduced":["0"],"last_affected":[],"package":"lxc","purl":"pkg:rpm/suse/lxc\u0026distro=SUSE%20Package%20Hub%2015%20SP5","source":"openSUSE-SU-2024:0342-1"},{"ecosystem":"SUSE:Package Hub 15 SP6","fixed":["6.0.2-bp156.2.3.1"],"introduced":["0"],"last_affected":[],"package":"lxc","purl":"pkg:rpm/suse/lxc\u0026distro=SUSE%20Package%20Hub%2015%20SP6","source":"openSUSE-SU-2024:0342-1"},{"ecosystem":"openSUSE:Leap 15.5","fixed":["6.0.2-bp156.2.3.1"],"introduced":["0"],"last_affected":[],"package":"lxc","purl":"pkg:rpm/opensuse/lxc\u0026distro=openSUSE%20Leap%2015.5","source":"openSUSE-SU-2024:0342-1"},{"ecosystem":"openSUSE:Leap 15.6","fixed":["6.0.2-bp156.2.3.1"],"introduced":["0"],"last_affected":[],"package":"lxc","purl":"pkg:rpm/opensuse/lxc\u0026distro=openSUSE%20Leap%2015.6","source":"openSUSE-SU-2024:0342-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["5.0.2-1.1"],"introduced":["0"],"last_affected":[],"package":"lxc","purl":"pkg:rpm/opensuse/lxc\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:12935-1"}],"prev":{"headline":"OpenStack Cinder, glance, and Nova vulnerable to Path Traversal","id":"CVE-2022-47951"},"products":["n/a"],"published":"2023-01-01","related":[{"cvss_score":9.1,"headline":"Path traversal in LXC before 1.0.9 and 2.x before 2.0.6","id":"CVE-2016-8649","kev_date_added":null,"published":"2017-05-01"},{"cvss_score":8.6,"headline":"Privilege escalation in n/a","id":"CVE-2016-10124","kev_date_added":null,"published":"2017-01-09"},{"cvss_score":8.1,"headline":"Supply chain in n/a","id":"CVE-2017-18641","kev_date_added":null,"published":"2020-02-10"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2013-6441","kev_date_added":null,"published":"2014-02-14"},{"cvss_score":4.9,"headline":"Path traversal in n/a","id":"CVE-2015-1331","kev_date_added":null,"published":"2015-08-12"},{"cvss_score":4.6,"headline":"Privilege escalation in n/a","id":"CVE-2015-1334","kev_date_added":null,"published":"2015-08-12"},{"cvss_score":4.3,"headline":"lxc lxc-user-nic insufficient ownership validation allows cross-tenant OVS port deletion","id":"CVE-2026-39402","kev_date_added":null,"published":"2026-05-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-10","vendors":["n/a"]},"summary":"Local attackers can infer file existence in protected directories via error message differences in the setuid lxc-user-nic binary.","url":"https://insights.sbomify.com/CVE-2022-47952/"}