SafeLine SL6/SL6+ up to 4.96 Device Configuration authentication bypass

Summaryinfo

A vulnerability identified as critical has been detected in SafeLine SL6 and SL6+ up to 4.96. This vulnerability affects unknown code of the component Device Configuration Handler. This manipulation causes authentication bypass. This vulnerability is handled as CVE-2025-4994. The attack can only be done within the local network. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in SafeLine SL6 and SL6+ up to 4.96. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component Device Configuration Handler. The manipulation with an unknown input leads to a authentication bypass vulnerability. The CWE definition for the vulnerability is CWE-305. The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The SafeLine SL6 and SL6+ devices integrated into elevator emergency intercom systems are vulnerable to an authentication bypass. This vulnerability allows attackers to bypass authentication requirements and access the device's configuration service via the Bluetooth Low Energy (BLE) interface. Consequently, an attacker within wireless range can gain unauthorized administrative access to the device configuration.

The weakness was released by Jan Hüber. The advisory is shared at schutzwerk.com. This vulnerability is known as CVE-2025-4994 since 05/20/2025. The exploitation appears to be easy. The attack can only be initiated within the local network. Neither technical details nor an exploit are publicly available.

Upgrading to version 4.97 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• SafeLine

Name

• SL6
• SL6+

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5
• 4.6
• 4.7
• 4.8
• 4.9
• 4.10
• 4.11
• 4.12
• 4.13
• 4.14
• 4.15
• 4.16
• 4.17
• 4.18
• 4.19
• 4.20
• 4.21
• 4.22
• 4.23
• 4.24
• 4.25
• 4.26
• 4.27
• 4.28
• 4.29
• 4.30
• 4.31
• 4.32
• 4.33
• 4.34
• 4.35
• 4.36
• 4.37
• 4.38
• 4.39
• 4.40
• 4.41
• 4.42
• 4.43
• 4.44
• 4.45
• 4.46
• 4.47
• 4.48
• 4.49
• 4.50
• 4.51
• 4.52
• 4.53
• 4.54
• 4.55
• 4.56
• 4.57
• 4.58
• 4.59
• 4.60
• 4.61
• 4.62
• 4.63
• 4.64
• 4.65
• 4.66
• 4.67
• 4.68
• 4.69
• 4.70
• 4.71
• 4.72
• 4.73
• 4.74
• 4.75
• 4.76
• 4.77
• 4.78
• 4.79
• 4.80
• 4.81
• 4.82
• 4.83
• 4.84
• 4.85
• 4.86
• 4.87
• 4.88
• 4.89
• 4.90
• 4.91
• 4.92
• 4.93
• 4.94
• 4.95
• 4.96

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion