The vulnerability lies in two main areas: logging of sensitive information and incomplete data cleanup. The analysis of the patch 722938bb6a97e8b8a5678e6858e44c4d505c08ee confirms this.
First, multiple functions across the application were logging potentially sensitive data, such as server URLs, deep-linking URLs, certificate details, and server configuration objects. An attacker with local file system access could read these logs to gather information about the servers the user is connected to. The patch addresses this by systematically removing this data from log calls in functions like handleAppCertificateError, handleServerURLValidation, and generateHandleConsoleMessage. The generateHandleConsoleMessage function is particularly notable as it now sanitizes renderer process logs to strip out hostnames.
Second, the application failed to clear session data when a server was removed. The ServerManager.removeServer function would delete the server from the configuration but left the corresponding cookies, local storage, and other session data on disk. The patch introduces a new function, ServerHub.handleServerCleanup, which explicitly calls session.defaultSession.clearData for the removed server's origin. This cleanup is triggered by an event now emitted from the removeServer function, closing the data leakage gap.