ConneXium Network Manager Software (All Versions)

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

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2021-22801	11 Feb 2022	ConneXium Network Manager Software (All Versions)	Customers can protect their installation with the following: • STEP 1: Download and run the CNM Alarms Disabler Tool here: https://www.se.com/us/en/download/document/CNM_Alarms_Disabler_Tool/ Usage: Place the disabler tool and the .cxn project file in the same directory. In a shell prompt, and in the chosen directory, execute the following command: disabler -projectfile {source project filename} -resultfile {converted project filename} Important: The converter secures and modifies the CNM database and store it in a new project file. Before a database coming from an untrusted source is loaded into CNM, customers must run the converter. Note that the original database is not modified. So if the original database needs to be loaded once more, it must be converted first. STEP 2: Set up the “Edit Password” in the CNM software (https://www.se.com/ww/en/product-range/61527-connexium-network-manager/#software-and-firmware). The “Edit Mode” is enabled by default. Customers must activate the edit protection by switching to “Run mode” before exiting the application. Please refer to the chapter “Edit Mode” of the user manual.	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.