{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-3151 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2011-3151 yet. Limit exposure of the affected software until one is available.","what":"CVE-2011-3151 is a medium-severity vulnerability in n/a, published on 22 Apr 2019. 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-2011-3151 and fix it if it is affected.\n\nWhat it is: CVE-2011-3151 is a medium-severity vulnerability in n/a, published on 22 Apr 2019. 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-2011-3151 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-2011-3151/ (Markdown: https://insights.sbomify.com/CVE-2011-3151/index.md)","id":"CVE-2011-3151","markdown":"https://insights.sbomify.com/CVE-2011-3151/index.md","name":"CVE-2011-3151","record":{"aliases":["GHSA-3wp7-vqr4-g72h"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Ubuntu SELinux initscript","requires_auth":"low_privilege","summary":"An attacker can exploit a world-writable lockfile creation flaw in the Ubuntu SELinux initscript to allocate zero-byte files on writable filesystems if kernel symlink protections are disabled.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"selinux","vendor":"canonical"}],"cvss":{"score":5.2,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"The Ubuntu SELinux initscript before version 1:0.10 used touch to create a lockfile in a world-writable directory. If the OS kernel does not have symlink protections then an attacker can cause a zero byte file to be allocated on any writable filesystem.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SELinux initscript misuse of touch","id":"CVE-2011-3151","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2011"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2011-3152"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2011-3150"},"products":["n/a"],"published":"2019-04-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"An attacker can exploit a world-writable lockfile creation flaw in the Ubuntu SELinux initscript to allocate zero-byte files on writable filesystems if kernel symlink protections are disabled.","url":"https://insights.sbomify.com/CVE-2011-3151/"}