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

Schneider Electric

SpaceLogic AS-P

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-5557 12 Jun 2024 V5.0.3 and prior Version 6.0.1 or greater of SpaceLogic AS-P and AS-B includes a fix for this vulnerability and is available for download here: https://ecoxpert.se.com/en/softwarecenter/ building-automation/ebo-system/building-operation- 2024-version-6.0 Hotfix patches are also available for versions 5.0.3 and 4.0.5 here: https://community.se.com/t5/EBO-Hotfix-List/bgp/ sbo-hotfix-list Step1: Locate the version you need to patch on the Exchange Community using the links above. Step 2: Follow the instructions in the readme file. Update reference ↗
CVE-2024-5558 12 Jun 2024 V5.0.3 and prior Version 6.0.1 or greater of SpaceLogic AS-P and AS-B includes a fix for this vulnerability and is available for download here: https://ecoxpert.se.com/en/softwarecenter/ building-automation/ebo-system/building-operation- 2024-version-6.0 Hotfix patches are also available for versions 5.0.3 and 4.0.5 here: https://community.se.com/t5/EBO-Hotfix-List/bgp/ sbo-hotfix-list Step1: Locate the version you need to patch on the Exchange Community using the links above. Step 2: Follow the instructions in the readme file. 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.