CVE-2018-19637: Static temporary filename allows overwriting of files
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: supportutils (openSUSE:Tumbleweed) 3.1.17-2.2; supportutils (SUSE:Linux Enterprise Module for Basesystem 15) 3.1-5.7.1; hostinfo (SUSE:OpenStack Cloud 7) 1.0.1-19.5.1.
- Severity is disputed: the assigning authority (CNA) scores it 2.8, NVD 5.5.
Low priority for now. Upgrade to supportutils (openSUSE:Tumbleweed) 3.1.17-2.2; supportutils (SUSE:Linux Enterprise Module for Basesystem 15) 3.1-5.7.1; hostinfo (SUSE:OpenStack Cloud 7) 1.0.1-19.5.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Supportutils, before version 3.1-5.7.1, wrote data to static file /tmp/supp_log, allowing local attackers to overwrite files on systems without symlink protection
- Published
- Mar 5, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-377
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 5.5
- CNA · microfocus
- 2.8
- 2.7 point gap
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| opensuse | supportutils | cpe:2.3:a:opensuse:supportutils |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microfocus). Independent of NVD's CPE analysis and usually ahead of it.
SUSE supportutils
- unspecified and later · before 3.1-5.7.1affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opensuse supportutilsbefore 3.1-5.7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Tumbleweed | supportutils | before 3.1.17-2.2 | 3.1.17-2.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 | supportutils | before 3.1-5.7.1 | 3.1-5.7.1 |
| SUSE:OpenStack Cloud 7 | hostinfo | before 1.0.1-19.5.1 | 1.0.1-19.5.1 |
| SUSE:OpenStack Cloud 7 | supportutils | before 3.0-95.21.1 | 3.0-95.21.1 |
Same product
opensuse: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-19639Code execution if run with command line switch -v31Monitor
- CVE-2018-19636Local root exploit via inclusion of attacker controlled shell script31Monitor
- CVE-2018-19640Code execution if run with command line switch -v22Monitor
Published before and after this one in the same product
- Later →CVE-2018-19638Mar 5, 2019 · User can overwrite arbitrary log files in support tar18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:supportutils | 3.1.17-2.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:hostinfo | 1.0.1-19.5.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
| suse:supportutils | 3.1-5.7.1 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Vítězslav ČížekSUSE
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-377 · Insecure Temporary FileCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.