Moxa Service Missing Authentication for Critical Function
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 14, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 41th percentile
- CWE
- CWE-306
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Moxa
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| moxa | edr-8010 | cpe:2.3:a:moxa:edr-8010 |
| moxa | edr-g9010 | cpe:2.3:a:moxa:edr-g9010 |
| moxa | nat-102 | cpe:2.3:a:moxa:nat-102 |
| moxa | tn-4900 | cpe:2.3:a:moxa:tn-4900 |
| moxa | oncell g4302-lte4 | cpe:2.3:a:moxa:oncell_g4302-lte4 |
| moxa | edf-g1002-bp | cpe:2.3:a:moxa:edf-g1002-bp |
| moxa | edr-g9004 | cpe:2.3:a:moxa:edr-g9004 |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Moxa). Independent of NVD's CPE analysis and usually ahead of it.
Moxa EDF-G1002-BP Series
- 1.0 and later · up to and including 3.12.1affected
Moxa EDR-8010 Series
- 1.0 and later · up to and including 3.12.1affected
Moxa EDR-G9004 Series
- 1.0 and later · up to and including 3.12.1affected
Moxa EDR-G9010 Series
- 1.0 and later · up to and including 3.12.1affected
Moxa EDS-405A Series
- 3.14.4not affected
- 1.0 and later · up to and including 3.14affected
Moxa EDS-408A Series
- 3.14.6not affected
- 1.0 and later · up to and including 3.12affected
Moxa EDS-505A Series
- 1.0 and later · up to and including 3.11affected
Moxa EDS-508A Series
- 1.0 and later · up to and including 3.11affected
Moxa EDS-510A Series
- 1.0 and later · up to and including 3.12affected
Moxa EDS-510E Series
- 1.0 and later · up to and including 5.5affected
Moxa EDS-516A Series
- 1.0 and later · up to and including 3.11affected
Moxa EDS-518A Series
- 1.0 and later · up to and including 3.11affected
Same product
moxa: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-9140Moxa’s cellular routers, secure routers, and network security appliances are affected by a critical vulnerability, CVE-2024-9140.38Monitor
- CVE-2026-3868An improper handling of the length parameter inconsistency vulnerability has been identified in Moxa’s Secure Router.34Monitor
- CVE-2024-9139OS Command Injection in Restricted Command34Monitor
Published before and after this one in the same product
- Later →CVE-2026-3867Apr 27, 2026 · An improper ownership management vulnerability has been identified in Moxa’s Secure Router.24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Lars Haulinfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
—
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2024-91390 days apartOS Command Injection in Restricted Command34Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1697 · Oct 15, 2024(Moxa Çoklu Ürün Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-306 · Missing Authentication for Critical FunctionCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”
The bug in code
The whole CWE-306 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
// Added for the support teamapp.post("/maintenance/reset", resetDevice);Fixed
if (config.maintenanceEnabled) { app.post( "/maintenance/reset", requireSession, requireRole("admin"), resetDevice );}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.