MIK CryptX up to 0.064 on Perl LibTomCrypt vulnerable third-party component

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in MIK CryptX up to 0.064 on Perl. This affects an unknown part of the component LibTomCrypt. This manipulation causes vulnerable third-party component. This vulnerability is registered as CVE-2025-40912. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in MIK CryptX up to 0.064 on Perl. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component LibTomCrypt. The manipulation with an unknown input leads to a vulnerable third-party component vulnerability. The CWE definition for the vulnerability is CWE-1395. The product has a dependency on a third-party component that contains one or more known vulnerabilities. The impact remains unknown. The summary by CVE is:

CryptX for Perl before version 0.065 contains a dependency that may be susceptible to malformed unicode. CryptX embeds the tomcrypt library. The versions of that library in CryptX before 0.065 may be susceptible to CVE-2019-17362.

The advisory is shared at github.com. This vulnerability is known as CVE-2025-40912 since 04/16/2025. Neither technical details nor an exploit are publicly available.

Upgrading to version 0.065 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-18140). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Vulnerable third-party component
CWE: CWE-1395
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: CryptX 0.065

Timelineinfo

04/16/2025 🔍
06/11/2025 +56 days 🔍
06/11/2025 +0 days 🔍
06/12/2025 +1 days 🔍

Sourcesinfo

Advisory: 507
Status: Confirmed

CVE: CVE-2025-40912 (🔍)
GCVE (CVE): GCVE-0-2025-40912
GCVE (VulDB): GCVE-100-312325
EUVD: 🔍

Entryinfo

Created: 06/11/2025 20:41
Updated: 06/12/2025 02:36
Changes: 06/11/2025 20:41 (56), 06/12/2025 02:36 (1)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!