EDR-8010 Series: Missing Authentication for Critical Functionality
CVE-2024-9137 is a critical-severity missing authentication for critical functionality vulnerability in EDR-8010 Series from Moxa, with a CVSS 3.1 base score of 9.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected EDR-8010 Series versions: 1.0 through 3.12.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of EDR-8010 Series you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on moxa.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Moxa | EDR-8010 Series | 1.0 through 3.12.1 | Not stated |
| Moxa | EDR-G9004 Series | 1.0 through 3.12.1 | Not stated |
| Moxa | EDR-G9010 Series | 1.0 through 3.12.1 | Not stated |
| Moxa | EDF-G1002-BP Series | 1.0 through 3.12.1 | Not stated |
| Moxa | NAT-102 Series | 1.0 through 1.0.5 | Not stated |
| Moxa | OnCell G4302-LTE4 Series | 1.0 through 3.9 | Not stated |
| Moxa | TN-4900 Series | 1.0 through 3.6 | Not stated |
| Moxa | EDS-608 Series | 1.0 through 3.12 | Not stated |
| Moxa | EDS-611 Series | 1.0 through 3.12 | Not stated |
| Moxa | EDS-616 Series | 1.0 through 3.12 | Not stated |
| Moxa | EDS-619 Series | 1.0 through 3.12 | Not stated |
| Moxa | EDS-405A Series | 1.0 through 3.14 | Not stated |
| Moxa | EDS-408A Series | 1.0 through 3.12 | Not stated |
| Moxa | EDS-505A Series | 1.0 through 3.11 | Not stated |
| Moxa | EDS-508A Series | 1.0 through 3.11 | Not stated |
| Moxa | EDS-510A Series | 1.0 through 3.12 | Not stated |
| Moxa | EDS-516A Series | 1.0 through 3.11 | Not stated |
| Moxa | EDS-518A Series | 1.0 through 3.11 | Not stated |
| Moxa | EDS-G509 Series | 1.0 through 3.10 | Not stated |
| Moxa | EDS-P510 Series | 1.0 through 3.11 | Not stated |
| Moxa | EDS-P510A Series | 1.0 through 3.11 | Not stated |
| Moxa | EDS-510E Series | 1.0 through 5.5 | Not stated |
| Moxa | EDS-518E Series | 1.0 through 6.3 | Not stated |
| Moxa | EDS-528E Series | 1.0 through 6.3 | Not stated |
| Moxa | EDS-G508E Series | 1.0 through 6.4 | Not stated |
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H. Scored by CNA (moxa.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.8 | High | CNA (moxa.com) |
| CVSS 3.1 | 9.4 | Critical | CNA (moxa.com) |
Official description
The affected product lacks an authentication check when sending commands to the server via the Moxa service. This vulnerability allows an attacker to execute specified commands, potentially leading to unauthorized downloads or uploads of configuration files and system compromise.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in EDR-8010 Series
- 8.7 High severity
- 9.9 Critical severity
- 9.3 Critical severity
- 9.3 Critical severity
- 8.7 High severity
- 8.6 High severity
Recent Missing Authentication for Critical Functionality vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.