CVE-2025-41759

An administrator may attempt to block all networks by specifying "\" or "all" as the network identifier. However, these values are not supported and do not trigger any validation error. Instead, they are silently interpreted as network 0 which results in no networks being blocked at all...

EUVD-2025-208365

An administrator may attempt to block all networks by specifying "" or "all" as the network identifier. However, these values are not supported and do not trigger any validation error. Instead, they are silently interpreted as network 0 which results in no networks being blocked at all...

CVE-2025-41759

CVE-2025-41759 describes a logic issue in the block-list handling where using a wildcard, i.e., "*" or "all", to block networks is silently treated as network 0, resulting in no networks being blocked. The description does not specify affected products, versions, or root cause beyond this interpr...

CVE-2025-41759 Use of wildcard (“*” or “all”) in Block list

An administrator may attempt to block all networks by specifying "" or "all" as the network identifier. However, these values are not supported and do not trigger any validation error. Instead, they are silently interpreted as network 0 which results in no networks being blocked at all...

CVE-2025-41759 Use of wildcard (“*” or “all”) in Block list

An administrator may attempt to block all networks by specifying "" or "all" as the network identifier. However, these values are not supported and do not trigger any validation error. Instead, they are silently interpreted as network 0 which results in no networks being blocked at all...