{"answers":{"affected":"2 open source packages ship an affected version, including coreos-installer. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-3917 in the wild and no public exploit code.","fix":"Upgrade coreos-installer to 0.10.0 or later.","what":"CVE-2021-3917 is a medium-severity vulnerability in coreos-installer, published on 23 Aug 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-3917 and fix it if it is affected.\n\nWhat it is: CVE-2021-3917 is a medium-severity vulnerability in coreos-installer, published on 23 Aug 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-3917 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- coreos-installer (crates.io): affected all versions; fixed in 0.10.0\n- coreos-installer (crates.io): affected all versions; fixed in 0.10.0\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-3917/ (Markdown: https://insights.sbomify.com/CVE-2021-3917/index.md)","id":"CVE-2021-3917","markdown":"https://insights.sbomify.com/CVE-2021-3917/index.md","name":"CVE-2021-3917","record":{"aliases":["GHSA-862g-9h5m-m3qv"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CoreOS installer","requires_auth":"low_privilege","summary":"Local attackers can read sensitive Ignition configuration data due to world-readable file permissions in the CoreOS installer.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"coreos-installer","vendor":"redhat"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"A flaw was found in the coreos-installer, where it writes the Ignition config to the target system with world-readable access permissions. This flaw allows a local attacker to have read access to potentially sensitive data. The highest threat from this vulnerability is to confidentiality.","ecosystems":["crates.io"],"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":"coreos-installer \u003c 0.10.0 writes world-readable Ignition config to installed system","id":"CVE-2021-3917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":2,"n_references":4,"next":{"headline":"Prototype Pollution in kriszyp/json-schema","id":"CVE-2021-3918"},"packages":[{"ecosystem":"crates.io","fixed":["0.10.0"],"introduced":["0"],"last_affected":[],"package":"coreos-installer","purl":null,"source":"GHSA-862g-9h5m-m3qv"},{"ecosystem":"crates.io","fixed":["0.10.0"],"introduced":["0"],"last_affected":[],"package":"coreos-installer","purl":"pkg:cargo/coreos-installer","source":"GHSA-862g-9h5m-m3qv"}],"prev":{"headline":"Path Traversal in bookstackapp/bookstack","id":"CVE-2021-3916"},"products":["coreos-installer"],"published":"2022-08-23","related":[{"cvss_score":7.8,"headline":"coreos-installer improperly verifies GPG signature when decompressing gzipped artifact","id":"CVE-2021-20319","kev_date_added":null,"published":"2022-03-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-08-03","vendors":["n/a"]},"summary":"Local attackers can read sensitive Ignition configuration data due to world-readable file permissions in the CoreOS installer.","url":"https://insights.sbomify.com/CVE-2021-3917/"}