CVE-2025-40680
BaseFortify
Publication date: 2025-07-24
Last updated on: 2025-07-25
Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| capillary_io | capillaryscope | 2.5.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-311 | The product does not encrypt sensitive or critical information before storage or transmission. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in CapillaryScope version 2.5.0 involves the lack of encryption for sensitive data. Specifically, proxy credentials and JWT session tokens are stored in plaintext within Windows registry keys. As a result, any authenticated local user with read access to the registry can extract these sensitive values, potentially compromising security. [1]
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access to sensitive information such as proxy credentials and session tokens by any authenticated local user with registry read access. This could allow attackers to impersonate users, hijack sessions, or gain further access within the system, increasing the risk of data breaches or unauthorized actions. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if CapillaryScope version 2.5.0 or earlier is installed and by inspecting the Windows registry for plaintext storage of proxy credentials and JWT session tokens. Specifically, an authenticated local user with read access to the registry can look for these sensitive values stored in plaintext within various registry keys related to CapillaryScope. Commands such as 'reg query' in Windows PowerShell or Command Prompt can be used to examine these registry keys for unencrypted sensitive data. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade CapillaryScope to version 2.5.1 or later, where the vulnerability has been fixed by encrypting sensitive data stored in the registry. Until the upgrade is applied, restrict local user access to the registry keys where sensitive data is stored to prevent unauthorized reading of plaintext credentials and tokens. [1]