WIZVERA Veraport Race Condition Vulnerability

published 2018-12-20 7y ago modified 2026-06-17 4mo ago also EUVD-2018-16983

cvss: 8.0; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.4%; EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits: 0; none known

In Veraport G3 ALL on MacOS, a race condition when calling the Veraport API allow remote attacker to cause arbitrary file download and execution. This results in remote code execution.

Is CVE-2018-5198 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

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

CVSS scores

assigned by	version	score	vector
CNA	3.0	8.0	CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

WIZVERA Veraport

Classification

Weakness

CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

boho.or.kr /krcert/secNoticeView.do?bulletin_writing_sequence=30112
third-party-advisory

Sources

CVE List CVE-2018-5198
NVD CVE-2018-5198

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.