INVT HMITool VPM File Parser out-of-bounds write

Summaryinfo

A vulnerability has been found in INVT HMITool and classified as critical. This vulnerability affects unknown code of the component VPM File Parser. This manipulation causes out-of-bounds write. This vulnerability is handled as CVE-2025-7225. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in INVT HMITool (the affected version unknown). It has been declared as critical. Affected by this vulnerability is an unknown part of the component VPM File Parser. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

INVT HMITool VPM File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of INVT HMITool. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of VPM files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-25047.

The advisory is shared at zerodayinitiative.com. This vulnerability is known as CVE-2025-7225. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/29/2025).

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

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-22256). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• INVT

Name

• HMITool

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion