Evope Core 1.1.3.20 hard-coded key

Summaryinfo

A vulnerability identified as problematic has been detected in Evope Core 1.1.3.20. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in hard-coded key. This vulnerability is identified as CVE-2025-56577. The attack is only possible with local access. There is not any exploit available.

Detailsinfo

A vulnerability was found in Evope Core 1.1.3.20. It has been classified as problematic. This affects some unknown functionality. The manipulation with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality. The summary by CVE is:

An issue in Evope Core v.1.1.3.20 allows a local attacker to obtain sensitive information via the use of hard coded cryptographic keys.

The advisory is shared at packetstorm.news. This vulnerability is uniquely identified as CVE-2025-56577 since 08/17/2025. The exploitability is told to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Evope

Name

• Core

Version

• 1.1.3.20

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion