Publisher not identified
CodeMeter
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at codemeter, but registry activity is not a publisher support boundary.
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-2020-16233 | 16 Sep 2020 | All versions prior to 7.10 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2020-14513 | 16 Sep 2020 | All versions prior to 6.81 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2020-14515 | 16 Sep 2020 | All versions prior to 6.90 when using CmActLicense update files with CmActLicense Firm Code. | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2020-14519 | 16 Sep 2020 | All versions prior to 7.00, including Version 7.0 or newer with the affected WebSockets API still enabled. This is especially relevant for systems or devices where a web browser is used to access a web server. | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2020-14517 | 16 Sep 2020 | All versions prior to 6.90, including Version 6.90 or newer only if CodeMeter Runtime is running as server. | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2020-14509 | 16 Sep 2020 | All versions prior to 7.10 | No fixed version is explicitly recorded in the structured CVE data. | 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.