CVE-2025-2810
BaseFortify
Publication date: 2025-08-05
Last updated on: 2025-08-05
Assigner: CERT VDE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| drΓ€ger | icmhelper | 1.4.0.1 |
| drΓ€ger | icmhelper | 2.0.1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-321 | The product uses a hard-coded, unchangeable cryptographic key. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow an attacker to escalate privileges and gain full access to the application, sensitive information, client systems, and servers. This can compromise confidentiality and potentially lead to further attacks with higher severity impacts. [1]
Can you explain this vulnerability to me?
This vulnerability involves a low privileged local attacker abusing a service by using a hardcoded cryptographic key. The hardcoded key allows the attacker to exploit the service, which can lead to further privilege escalation and unauthorized access. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying the presence of the affected service using the hardcoded cryptographic key. Since the vulnerability is local and involves abuse of a hardcoded key in the ICMHelper service, detection can include checking the version of the ICMHelper service installed on your system. Specifically, versions up to 1.4.0.1 are affected. You can use commands to check the installed version of the service, for example, on Windows: 'sc query ICMHelper' or checking the executable properties. Additionally, searching for the presence of the hardcoded key in the service binaries or configuration files might help, but no specific commands are provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the ICMHelper service to version 2.0.1.0 or later, where the vulnerability has been fixed. Until the update can be applied, restrict local access to the affected system to trusted users only, as exploitation requires local access. Monitoring and limiting permissions for low-privileged users can also reduce risk. [1]