SICK AG
SICK InspectorP61x
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-2024-10776 | 6 Dec 2024 | < <5.0.0 | Customers are strongly recommended to upgrade to the latest release. Furthermore, the app development should be done in a trusted environment. After the development, app management should be disabled. | Update reference ↗ |
| CVE-2024-10774 | 6 Dec 2024 | < <5.0.0 | Customers are strongly recommended to upgrade to the latest release. Furthermore, the app development for which the CROWN API is required should be done in a trusted environment. As soon as the device is used productively with the custom-developed apps, the CROWN API should be deactivated. | Update reference ↗ |
| CVE-2024-10773 | 6 Dec 2024 | < <5.0.0; < <5.10.0 | Customers are strongly recommended to upgrade to the latest release. | Update reference ↗ |
| CVE-2024-10772 | 6 Dec 2024 | < <5.0.0 | Customers are strongly recommended to upgrade to the latest release. | Update reference ↗ |
| CVE-2024-10771 | 6 Dec 2024 | < <5.0.0; < <5.10.0; all versions | Customers are strongly recommended to upgrade to the latest release. | Update reference ↗ |
| CVE-2024-11022 | 6 Dec 2024 | all versions | 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.