# SUSE-SU-2021:3527-1: Security update for wireguard-tools

> Local attackers can read WireGuard configuration files due to world-readable permissions on the configuration directory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Oct 2021

## What is SUSE-SU-2021:3527-1?

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.

### Official description

This update for wireguard-tools fixes the following issues:

- Removed world-readable permissions from /etc/wireguard (bsc#1191224)

## Which versions are affected by SUSE-SU-2021:3527-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wireguard-tools` | SUSE:Linux Enterprise Module for Basesystem 15 SP2 | All versions | 1.0.20200827-5.9.1 |
| `wireguard-tools` | SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 1.0.20200827-5.9.1 |

## How do I fix SUSE-SU-2021:3527-1?

Apply the vendor's patch.

## Is SUSE-SU-2021:3527-1 being exploited?

There is no known exploitation of SUSE-SU-2021:3527-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2021:3527-1 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of SUSE-SU-2021:3527-1 in the wild and no public exploit code.

Affected product: wireguard-tools. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/SUSE-SU-2021-3527-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2021-3527-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2021:3527-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2021-3527-1/
Summaries are generated and may contain mistakes; the official description above is the record.