Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY5 SECURITY RECORDS

AutomationDirect

C-More EA9

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2024-11611 30 Jan 2025 6.78 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-11610 30 Jan 2025 6.78 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-11609 30 Jan 2025 6.78 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2006 31 Aug 2022 EA9-T6CL < 6.73; EA9-T6CL-R < 6.73; EA9-T7CL < 6.73; EA9-T7CL-R < 6.73; EA9-T8CL < 6.73; EA9-T10CL < 6.73; EA9-T10WCL < 6.73; EA9-T12CL < 6.73 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-2005 31 Aug 2022 EA9-T6CL < 6.73; EA9-T6CL-R < 6.73; EA9-T7CL < 6.73; EA9-T7CL-R < 6.73; EA9-T8CL < 6.73; EA9-T10CL < 6.73; EA9-T10WCL < 6.73; EA9-T12CL < 6.73 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗

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.