CVE-2025-60791
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-27

Last updated on: 2025-10-30

Assigner: MITRE

Description
Easywork Enterprise 2.1.3.354 is vulnerable to Cleartext Storage of Sensitive Information in Memory. The application leaves valid device-bound license keys in process memory after a failed activation attempt. The keys can be obtained by attaching a debugger or analyzing the process/memory dump and then they can be used to activate the software on the same machine without purchasing.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-27
Last Modified
2025-10-30
Generated
2026-05-07
AI Q&A
2025-10-27
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
easywork enterprise 2.1.3.354
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-316 The product stores sensitive information in cleartext in memory.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

Easywork Enterprise 2.1.3.354 has a vulnerability where valid device-bound license keys remain in the process memory after a failed activation attempt. An attacker can extract these keys by attaching a debugger or analyzing the process memory dump, allowing them to activate the software on the same machine without purchasing a license.


How can this vulnerability impact me? :

This vulnerability can allow unauthorized users to obtain valid license keys from memory and activate the software without paying for it, potentially leading to software piracy and loss of revenue for the software vendor.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by analyzing the process memory of Easywork Enterprise 2.1.3.354 after a failed activation attempt. You can attach a debugger to the running process or create a memory dump and search for device-bound license keys stored in cleartext. Specific commands depend on your operating system and tools, but examples include using 'gdb' or 'procmon' on Windows, or 'gdb' and 'strings' on Linux to inspect process memory.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include avoiding failed activation attempts on Easywork Enterprise 2.1.3.354 to prevent license keys from being left in memory, restricting debugger and memory dump access to trusted users only, and monitoring for unauthorized debugging or memory analysis activities. Additionally, consider updating the software if a patched version becomes available.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart