CVE-2018-19637 [Low] | Security Vulnerability in Supportutils

CVE-2018-19637 is rated Low Risk (12.3/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.04%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2023-03-07	0.89%	0.04%	-0.84%
2	2022-02-04	0.33%	0.89%	+0.55%
3	2021-04-14	—	0.33%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2023-03-07

0.89%

0.04%

-0.84%

2022-02-04

0.33%

0.89%

+0.55%

2021-04-14

—

0.33%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
2.8	3.0	LOW	`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.3	1.4	[email protected]
5.5	3.0	MEDIUM	`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	1.8	3.6	[email protected]
3.6	2.0	LOW	`AV:L/AC:L/Au:N/C:N/I:P/A:P` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:N) No confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	3.9	4.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

2.8

3.0

LOW

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.3

1.4

[email protected]

5.5

3.0

MEDIUM

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

1.8

3.6

[email protected]

3.6

2.0

LOW

AV:L/AC:L/Au:N/C:N/I:P/A:P Click to expand

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:N): No confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

3.9

4.9

[email protected]

OS Trackers for CVE-2018-19637

vendor	priority	summary	link
`suse`	high	CVE-2018-19637 severity important: SUSE including 252 source package names (10.1-4.1:supportutils-3.1-5.7.1, amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, …), 344 product×package rows across 78 product lines (Container suse/sle-micro/5.0/toolbox, Image SLES12-SP5-Azure-BYOS, … (78 product lines)): Fixed 164, Known Affected 157, Known Not Affected 23.	https://www.suse.com/security/cve/CVE-2018-19637/

Affected software / configurations for CVE-2018-19637

Vendor	Product	Version	Raw CPE
opensuse	supportutils	< 3.1-5.7.1	cpe:2.3:a:opensuse:supportutils::::::::

References for CVE-2018-19637

URL	Tags
http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00018.html
https://bugzilla.suse.com/show_bug.cgi?id=1117776

URL

CVE-2018-19637 | Static temporary filename allows overwriting of files

Exploit prediction scoring system (EPSS) score for CVE-2018-19637

Common vulnerability scoring system (CVSS) metrics for CVE-2018-19637

Weakness enumeration for CVE-2018-19637

OS Trackers for CVE-2018-19637

Affected software / configurations for CVE-2018-19637

References for CVE-2018-19637