{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22566 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-22566 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22566 is a medium-severity vulnerability in Google LLC Fuchsia, published on 18 Jan 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-2021-22566 and fix it if it is affected.\n\nWhat it is: CVE-2021-22566 is a medium-severity vulnerability in Google LLC Fuchsia, published on 18 Jan 2022. 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-2021-22566 in the wild and no public exploit code.\n\nAffected product: Google LLC Fuchsia. 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-2021-22566/ (Markdown: https://insights.sbomify.com/CVE-2021-22566/index.md)","id":"CVE-2021-22566","markdown":"https://insights.sbomify.com/CVE-2021-22566/index.md","name":"CVE-2021-22566","record":{"aliases":["GHSA-q77g-rg5g-rf78"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["security_bypass","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Fuchsia OS kernel","requires_auth":"none","summary":"Incorrect MMU flag mapping allows bypassing kernel and user-mode executability restrictions, facilitating privilege escalation in Fuchsia OS.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"fuchsia","vendor":"google"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-275","name":null}],"description":"An incorrect setting of UXN bits within mmu_flags_to_s1_pte_attr lead to privileged executable pages being mapped as executable from an unprivileged context. This can be leveraged by an attacker to bypass executability restrictions of kernel-mode pages from user-mode. An incorrect setting of PXN bits within mmu_flags_to_s1_pte_attr lead to unprivileged executable pages being mapped as executable from a privileged context. This can be leveraged by an attacker to bypass executability restrictions of user-mode pages from kernel-mode. Typically this allows a potential attacker to circumvent a mitigation, making exploitation of potential kernel-mode vulnerabilities easier. We recommend updating kernel beyond commit 7d731b4e9599088ac3073956933559da7bca6a00 and rebuilding.","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":"Incorrect mapping of Executable bits in Fuchsia Kernel","id":"CVE-2021-22566","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Bidirectional Override in Dart SDK","id":"CVE-2021-22567"},"packages":[],"prev":{"headline":"Insufficient Granularity of Access Control in GAEN Notification Server","id":"CVE-2021-22565"},"products":["Fuchsia"],"published":"2022-01-18","related":[{"cvss_score":7.5,"headline":"Write access to VMO data through copy-on-write in Fuchsia","id":"CVE-2022-0247","kev_date_added":null,"published":"2022-02-25"},{"cvss_score":6.9,"headline":"Identifiable Header Values In Fuchsia Leading To Tracking of The User","id":"CVE-2024-10604","kev_date_added":null,"published":"2025-01-30"},{"cvss_score":5.3,"headline":"Integer Overflow in Fuchsia Kernel","id":"CVE-2021-22556","kev_date_added":null,"published":"2022-05-03"},{"cvss_score":5.3,"headline":"Illegal access to Kernel log in Fuchsia","id":"CVE-2022-0882","kev_date_added":null,"published":"2022-05-03"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Google LLC"]},"summary":"Incorrect MMU flag mapping allows bypassing kernel and user-mode executability restrictions, facilitating privilege escalation in Fuchsia OS.","url":"https://insights.sbomify.com/CVE-2021-22566/"}