CVE-2018-12465 in the critical feed json
Remote Code Execution in Micro Focus Secure Messaging Gateway
published 2018-06-29 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-4435
- cvss
- 9.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 80.0%
- EPSS 80.0% chance of exploitation in 30 days, percentile 99.6%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
An OS command injection vulnerability in the web administration component of Micro Focus Secure Messaging Gateway (SMG) allows a remote attacker authenticated as a privileged user to execute arbitrary OS commands on the SMG server. This can be exploited in conjunction with CVE-2018-12464 to achieve unauthenticated remote code execution. Affects Micro Focus Secure Messaging Gateway versions prior to 471. It does not affect previous versions of the product that used GWAVA product name (i.e. GWAVA 6.5).
Patch / fix
- Micro Focus Secure Messaging Gateway 471
Timeline
- First public exploit (Metasploit exploit/linux/http/microfocus_secure_messaging_gateway)
- Published
Exploit prediction
80.02% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/linux/http/microfocus_secure_messaging_gateway MicroFocus Secure Messaging Gateway Remote Code Execution metasploit exploit, excellent rank, 2018-06-19
- EDB-45083 Micro Focus Secure Messaging Gateway (SMG) < 471 - Remote Code Execution (Metasploit) webapps, 2018-07-24
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Affected products
- Micro Focus Secure Messaging Gateway
Classification
References
Sources
- CVE List CVE-2018-12465
- NVD CVE-2018-12465
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.