LiveActive security incident?Get immediate response
CVE Record

CVE-2017-12121: An exploitable command injection vulnerability exists in the web server functionality of Moxa EDR-810 V4.1...

An exploitable command injection vulnerability exists in the web server functionality of Moxa EDR-810 V4.1 build 17030317. A specially crafted HTTP POST can cause a privilege escalation resulting in root shell. An attacker can inject OS commands into the rsakey\_name= parm in the "/goform/WebRSAKEYGen" uri to trigger this vulnerability.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-12121 lets an authenticated attacker reach the web server on a specific Moxa EDR-810 firmware build and make the device run operating-system commands. The reported impact is full device compromise with root-level control, so exposed management interfaces are the main business concern.

Executive priority

Treat as high priority for environments using this exact Moxa EDR-810 build. A successful attack could hand over root control of a network device, but current evidence in the provided sources does not show known active exploitation.

Technical view

Talos reported command injection in Moxa EDR-810 V4.1 build 17030317. The vulnerable web function accepts attacker-controlled input in the rsakey_name parameter and can execute OS commands, resulting in privilege escalation to a root shell. CVSS 3.0 is 8.8: network-reachable, low complexity, low privileges required, no user interaction.

Likely exposure

Exposure is likely limited to Moxa EDR-810 devices running V4.1 build 17030317 where the web management service is reachable by authenticated users. The provided sources do not identify other affected versions or products.

Exploitation context

The CVE record describes a crafted HTTP POST causing root-level command execution. CISA KEV status is false in the provided bundle, and no cited source here confirms active exploitation in the wild.

Researcher notes

The source bundle names one affected build and one vulnerable web server path/parameter. Avoid expanding scope beyond Moxa EDR-810 V4.1 build 17030317 without additional vendor evidence. Validate exposure by version, reachability, authentication model, and patch status.

Mitigation direction

  • Identify Moxa EDR-810 devices and confirm firmware build numbers.
  • Check Moxa and Talos guidance for fixed firmware or vendor-approved mitigations.
  • Restrict the web management interface to trusted administration networks only.
  • Remove any internet exposure for affected management interfaces.
  • Review administrative accounts and rotate credentials if exposure is suspected.

Validation and detection

  • Inventory devices for Moxa EDR-810 V4.1 build 17030317.
  • Verify management web access is blocked from untrusted networks.
  • Confirm vendor firmware or mitigation status through official guidance.
  • Review device logs for unexpected administrative actions or configuration changes.
  • Document residual exposure where patching is delayed.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-12121 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.8High
CVSS 3.0 vector shape for CVE-2017-12121Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TalosMoxaMoxa EDR-810 V4.1 build 17030317Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.