# CVE-2019-3687: "easy" permission profile allows everyone execute dumpcap and read all network traffic

> Local users can sniff network traffic if the 'easy' permission profile is enabled, allowing unauthorized data access.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 24 Jan 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q4cf-vq5x-23pq

## What is CVE-2019-3687?

CVE-2019-3687 is a medium-severity missing authorization vulnerability in Suse Linux Enterprise Server, published on 24 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The permission package in SUSE Linux Enterprise Server allowed all local users to run dumpcap in the "easy" permission profile and sniff network traffic. This issue affects: SUSE Linux Enterprise Server permissions versions starting from 85c83fef7e017f8ab7f8602d3163786d57344439 to 081d081dcfaf61710bda34bc21c80c66276119aa.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2019-3687?

It affects 1 product.


Products: Suse Linux Enterprise Server.

## How do I fix CVE-2019-3687?

Apply the vendor's patch.

## Is CVE-2019-3687 being exploited?

There is no known exploitation of CVE-2019-3687 in the wild and no public exploit code.

## Other vulnerabilities in Suse Linux Enterprise Server

- [CVE-2026-25702](https://insights.sbomify.com/CVE-2026-25702/): nftables disabled due to incorrect kernel backport (high 7.3)
- [CVE-2021-32000](https://insights.sbomify.com/CVE-2021-32000/): clone-master-clean-up: dangerous file system operations (low 3.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3687 and fix it if it is affected.

What it is: CVE-2019-3687 is a medium-severity missing authorization vulnerability in Suse Linux Enterprise Server, published on 24 Jan 2020. 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 CVE-2019-3687 in the wild and no public exploit code.

Affected product: Suse Linux Enterprise Server. 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/CVE-2019-3687/ (Markdown: https://insights.sbomify.com/CVE-2019-3687/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-3687
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-3687
- OSV: https://osv.dev/vulnerability/CVE-2019-3687

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-3687/
Summaries are generated and may contain mistakes; the official description above is the record.