Insecure API port exposed to all Master Node guest containers

published 2020-01-17 6y ago modified 2026-06-17 4mo ago also EUVD-2019-13317

cvss: 8.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

SUSE SUSE CaaS Platform 3.0 17.09.1_ce-7.6.1

Is CVE-2019-3682 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.4	CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	4.6	AV:L/AC:L/Au:N/C:P/I:P/A:P

Affected products

SUSE SUSE CaaS Platform 3.0

Classification

Weakness

CWE-668 Exposure of Resource to Wrong Sphere

References

bugzilla.suse.com /show_bug.cgi?id=1121148
permissions-required

Sources

CVE List CVE-2019-3682
NVD CVE-2019-3682

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.