← Search results
CVE-LINKED INVENTORY19 SECURITY RECORDS
Talos
Moxa
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2017-14439 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-14438 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-14437 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-14436 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-14435 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-14434 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-14433 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-14432 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12129 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12128 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12127 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12126 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12125 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12124 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12123 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12121 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-12120 | 14 May 2018 | Moxa EDR-810 V4.1 build 17030317 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-14459 | 11 Apr 2018 | Moxa AWK-3131A Industrial IEEE 802.11a/b/g/n wireless AP/bridge/client versions 1.4 - 1.9. In addition, versions prior to 1.4 appear similarly vulnerable to injection, but not as easily exploitable (described below). Other models in the AWK product line may likewise be vulnerable but have not been tested. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-8717 | 2 Apr 2018 | Moxa AWK-3131A Series Industrial IEEE 802.11a/b/g/n wireless AP/bridge/client 1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.