{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46179 exists.","fix":"No fix has been published for CVE-2022-46179 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46179 is a critical authentication bypass vulnerability in LiuWoodsCode LiuOS, published on 28 Dec 2022. 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-46179 and fix it if it is affected.\n\nWhat it is: CVE-2022-46179 is a critical authentication bypass vulnerability in LiuWoodsCode LiuOS, published on 28 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46179 exists.\n\nAffected product: LiuWoodsCode LiuOS. 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-46179/ (Markdown: https://insights.sbomify.com/CVE-2022-46179/index.md)","id":"CVE-2022-46179","markdown":"https://insights.sbomify.com/CVE-2022-46179/index.md","name":"CVE-2022-46179","record":{"aliases":["GHSA-f9x3-mj2r-cqmf"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Python OS simulation","requires_auth":"none","summary":"Attackers can bypass authentication in LiuOS by setting the GITHUB_ACTIONS environment variable to an unexpected value, allowing unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"liuos","vendor":"liuos_project"}],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"LiuOS is a small Python project meant to imitate the functions of a regular operating system. Version 0.1.0 and prior of LiuOS allow an attacker to set the GITHUB_ACTIONS environment variable to anything other than null or true and skip authentication checks. This issue is patched in the latest commit (c658b4f3e57258acf5f6207a90c2f2169698ae22) by requiring the var to be set to true, causing a test script to run instead of being able to login. A potential workaround is to check for the GITHUB_ACTIONS environment variable and set it to \"\" (no quotes) to null the variable and force credential checks.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"LiuOS vulnerable to Authorization Bypass through User-Controlled Key","id":"CVE-2022-46179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Arbitrary HTML injection in discourse-mermaid-theme-component","id":"CVE-2022-46180"},"packages":[],"prev":{"headline":"Path Traversal In MeterSpere allows file upload to any path","id":"CVE-2022-46178"},"products":["LiuOS"],"published":"2022-12-28","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-14","vendors":["LiuWoodsCode"]},"summary":"Attackers can bypass authentication in LiuOS by setting the GITHUB_ACTIONS environment variable to an unexpected value, allowing unauthorized access.","url":"https://insights.sbomify.com/CVE-2022-46179/"}