An issue was discovered in Ozeki NG SMS Gateway through 4.17.6.

published 2020-09-29 6y ago modified 2026-06-17 4mo ago also EUVD-2020-6196

cvss: 7.2; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.8%; EPSS 1.8% chance of exploitation in 30 days, percentile 79%
public exploits: 0; none known

An issue was discovered in Ozeki NG SMS Gateway through 4.17.6. It stores SMS messages in .NET serialized format on the filesystem. By generating (and writing to the disk) malicious .NET serialized files, an attacker can trick the product into deserializing them, resulting in arbitrary code execution.

Patch / fix

links 1

github.com/DrunkenShells/Disclosures/tree/master/CVE-2020-14030-RCE%2… advisory

Is CVE-2020-14030 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.84% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

References

github.com /DrunkenShells/Disclosures/tree/master/CVE-2020-14030-RCE%20via%20.NET%20Deserialization-Ozeki%20SMS%20Gateway
patch, third-party-advisory
ozeki.hu /index.php?owpn=231
vendor-advisory

Sources

CVE List CVE-2020-14030
NVD CVE-2020-14030

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.