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

HCL Software

DRYiCE MyXalytics

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-42181 12 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42180 12 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42179 12 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42175 11 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42174 11 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42173 11 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42172 11 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42171 11 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42170 11 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42169 11 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-42168 11 Jan 2025 6.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50347 10 Apr 2024 5.9, 6.0, 6.1, 6.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45722 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45724 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45723 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50341 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50342 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50343 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50344 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50345 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50346 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50348 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50350 3 Jan 2024 5.9, 6.0, 6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50351 3 Jan 2024 5.9, 6.0, 6.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.