CVE-2025-59098: Trace Functionality Leaking Sensitive Data in dormakaba access manager
The Access Manager is offering a trace functionality to debug errors and issues with the device. The trace functionality is implemented as a simple TCP socket. A tool called TraceClient.exe, provided by dormakaba via the Access Manager web interface, is used to connect to the socket and receive debug information. The data is permanently broadcasted on the TCP socket. The socket can be accessed without any authentication or encryption.
The transmitted data is based on the set verbosity level. The verbosity level can be set using the http(s) endpoint with the service interface password or with the guessable identifier of the device via the SOAP interface.
The transmitted data contains sensitive data like the Card ID as well as all button presses on Registration units. This allows an attacker with network level access to retrieve all entered PINs on a registration unit.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2025-59098?
CVE-2025-59098 is classified as a high severity vulnerability due to its potential to leak sensitive data.
How do I fix CVE-2025-59098?
To mitigate CVE-2025-59098, it is recommended to disable the trace functionality in the dormakaba Access Manager.
What types of sensitive data are at risk with CVE-2025-59098?
CVE-2025-59098 potentially exposes sensitive information that can include authentication credentials and user activity logs.
Which systems are affected by CVE-2025-59098?
CVE-2025-59098 affects the dormakaba Access Manager software, particularly those utilizing the trace functionality.
Is there a workaround for CVE-2025-59098?
Yes, implementing network restrictions and disabling access to the trace functionality serves as a temporary workaround for CVE-2025-59098.