VYPR
Unrated severityNVD Advisory· Published Mar 11, 2020· Updated Aug 4, 2024

CVE-2019-9102

CVE-2019-9102

Description

A predictable token generation mechanism in Moxa MGate MB3xxx series gateways allows remote attackers to bypass CSRF protection.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A predictable token generation mechanism in Moxa MGate MB3xxx series gateways allows remote attackers to bypass CSRF protection.

Vulnerability

The cross-site request forgery (CSRF) protection mechanism in Moxa MGate MB3170, MB3270, MB3280, MB3480, MB3660, and MB3180 series protocol gateways uses a predictable token generation mechanism. Affected firmware versions include MB3170 and MB3270 series firmware version 4.0 or lower, MB3280 and MB3480 series firmware version 3.0 or lower, MB3660 series firmware version 2.2 or lower, and MB3180 series firmware version 2.0 or lower [1][2].

Exploitation

A remote attacker can exploit this vulnerability without authentication by predicting the CSRF token. The predictable token generation allows the attacker to forge requests that bypass the CSRF protection, enabling actions on behalf of an authenticated user [1][2].

Impact

Successful exploitation allows the attacker to perform unauthorized actions on the device as if they were an authenticated user. This can lead to configuration changes, data manipulation, or further compromise of the gateway and connected systems [1].

Mitigation

Moxa has released firmware updates to address this vulnerability. Users should update to the following fixed versions: MB3170 and MB3270 series to version 4.1, MB3180 series to version 2.1, MB3280 and MB3480 series to version 3.1, and MB3660 series to version 2.3 [1]. No workarounds are provided; upgrading is the recommended mitigation.

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

7

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.