{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-2110 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2006-2110 is a low-severity vulnerability in n/a, published on 1 May 2006. 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-2006-2110 and fix it if it is affected.\n\nWhat it is: CVE-2006-2110 is a low-severity vulnerability in n/a, published on 1 May 2006. 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-2006-2110 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-2006-2110/ (Markdown: https://insights.sbomify.com/CVE-2006-2110/index.md)","id":"CVE-2006-2110","markdown":"https://insights.sbomify.com/CVE-2006-2110/index.md","name":"CVE-2006-2110","record":{"aliases":["DSA-1060-1","GHSA-jmmm-f4ch-325f"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux virtualization kernel","requires_auth":"low_privilege","summary":"Local guest users in Vserver can escalate privileges to guest-root by exploiting context capabilities, requiring kernel updates.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vserver","vendor":"virtual_private_server"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"Virtual Private Server (Vserver) 2.0.x before 2.0.2-rc18 and 2.1.x before 2.1.1-rc18 provides certain context capabilities (ccaps) that allow local guest users to perform operations that were only intended to be allowed by the guest-root.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Privilege escalation in n/a","id":"CVE-2006-2110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2006"},"n_packages":0,"n_references":8,"next":{"headline":"Information disclosure in n/a","id":"CVE-2006-2111"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2006-2109"},"products":["n/a"],"published":"2006-05-01","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Local guest users in Vserver can escalate privileges to guest-root by exploiting context capabilities, requiring kernel updates.","url":"https://insights.sbomify.com/CVE-2006-2110/"}