# CVE-2019-3682: Insecure API port exposed to all Master Node guest containers

> An insecure API port exposed on the Kubernetes master node allows local guest containers to escalate privileges or execute code.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jh4h-8jgf-wfh2

## What is CVE-2019-3682?

CVE-2019-3682 is a high-severity vulnerability in SUSE CaaS Platform 3.0, published on 17 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The docker-kubic package in SUSE CaaS Platform 3.0 before 17.09.1_ce-7.6.1 provided access to an insecure API locally on the Kubernetes master node.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Suse Caas Platform.

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

No fix has been published for CVE-2019-3682 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-3682 being exploited?

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

## Other vulnerabilities in SUSE CaaS Platform 3.0

- [CVE-2020-8030](https://insights.sbomify.com/CVE-2020-8030/): skuba: Insecure /tmp usage when joining node to cluster (low 3.6)
- [CVE-2020-8029](https://insights.sbomify.com/CVE-2020-8029/): skuba: Insecure handling of private key (low 2.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3682 is a high-severity vulnerability in SUSE CaaS Platform 3.0, published on 17 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-3682 in the wild and no public exploit code.

Affected product: SUSE CaaS Platform 3.0. 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-3682/ (Markdown: https://insights.sbomify.com/CVE-2019-3682/index.md)
```

## Sources

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

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