{"answers":{"affected":"","exploited":"There is no known exploitation of SUSE-SU-2021:3527-1 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"SUSE-SU-2021:3527-1 is a vulnerability in wireguard-tools, published on 26 Oct 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for SUSE-SU-2021:3527-1 and fix it if it is affected.\n\nWhat it is: SUSE-SU-2021:3527-1 is a vulnerability in wireguard-tools, published on 26 Oct 2021. 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 SUSE-SU-2021:3527-1 in the wild and no public exploit code.\n\nAffected product: wireguard-tools. 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/SUSE-SU-2021-3527-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2021-3527-1/index.md)","id":"SUSE-SU-2021:3527-1","markdown":"https://insights.sbomify.com/SUSE-SU-2021-3527-1/index.md","name":"SUSE-SU-2021:3527-1","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SUSE Linux","requires_auth":"none","summary":"Local attackers can read WireGuard configuration files due to world-readable permissions on the configuration directory.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This update for wireguard-tools fixes the following issues:\n\n- Removed world-readable permissions from /etc/wireguard (bsc#1191224)","ecosystems":["SUSE:Linux Enterprise Module for Basesystem 15 SP2","SUSE:Linux Enterprise Module for Basesystem 15 SP3"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Security update for wireguard-tools","id":"SUSE-SU-2021:3527-1","indexable":false,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP2","fixed":["1.0.20200827-5.9.1"],"introduced":["0"],"last_affected":[],"package":"wireguard-tools","purl":"pkg:rpm/suse/wireguard-tools\u0026distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP2","source":"SUSE-SU-2021:3527-1"},{"ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP3","fixed":["1.0.20200827-5.9.1"],"introduced":["0"],"last_affected":[],"package":"wireguard-tools","purl":"pkg:rpm/suse/wireguard-tools\u0026distro=SUSE%20Linux%20Enterprise%20Module%20for%20Basesystem%2015%20SP3","source":"SUSE-SU-2021:3527-1"}],"products":null,"published":"2021-10-26","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Local attackers can read WireGuard configuration files due to world-readable permissions on the configuration directory.","url":"https://insights.sbomify.com/SUSE-SU-2021-3527-1/"}