JP1/IT Desktop Management 2 - Manager: External Control of File Name or Path
CVE-2025-65115 is a critical-severity external control of file name or path vulnerability in JP1/IT Desktop Management 2 - Manager from Hitachi, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 13-50-02, 13-11-04, 13-10-07 as the first without the flaw, so updating JP1/IT Desktop Management 2 - Manager to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.62% chance of exploitation within 30 days, higher than 51% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update JP1/IT Desktop Management 2 - Manager to 13-50-02 or 13-11-04 or 13-10-07 or 13-01-07, whichever matches your release line, or a later version.
- Update JP1/IT Desktop Management 2 - Operations Director to 13-50-02 or 13-11-04 or 13-10-07 or 13-01-07, whichever matches your release line, or a later version.
- Read the advisory on hitachi.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Hitachi | JP1/IT Desktop Management 2 - Manager | 13-50 up to, but not including, 13-50-02; 13-11 up to, but not including, 13-11-04; 13-10 up to, but not including, 13-10-07; 13-01 up to, but not including, 13-01-07; 13-00 up to, but not including, 13-00-05; 12-60 up to, but not including, 12-60-12; 10-50 through 12-50-11 | 13-50-02, 13-11-04, 13-10-07, 13-01-07, 13-00-05, 12-60-12 |
| Hitachi | JP1/IT Desktop Management 2 - Operations Director | 13-50 up to, but not including, 13-50-02; 13-11 up to, but not including, 13-11-04; 13-10 up to, but not including, 13-10-07; 13-01 up to, but not including, 13-01-07; 13-00 up to, but not including, 13-00-05; 12-60 up to, but not including, 12-60-12; 10-50 through 12-50-11 | 13-50-02, 13-11-04, 13-10-07, 13-01-07, 13-00-05, 12-60-12 |
| Hitachi | Job Management Partner 1/IT Desktop Management 2 - Manager | 10-50 through 10-50-11 | Not stated |
| Hitachi | JP1/IT Desktop Management - Manager | 09-50 through 10-10-16 | Not stated |
| Hitachi | Job Management Partner 1/IT Desktop Management - Manager | 09-50 through 10-10-16 | Not stated |
| Hitachi | JP1/NETM/DM Manager | 09-00 through 10-20-02 | Not stated |
| Hitachi | JP1/NETM/DM Client | 09-00 through 10-20-02 | Not stated |
| Hitachi | Job Management Partner 1/Software Distribution Manager | 09-00 through 09-51-13 | Not stated |
| Hitachi | Job Management Partner 1/Software Distribution Client | 09-00 through 09-51-13 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | CNA (hitachi.co.jp) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
Remote Code Execution Vulnerability in JP1/IT Desktop Management 2 - Manager on Windows, JP1/IT Desktop Management 2 - Operations Director on Windows, Job Management Partner 1/IT Desktop Management 2 - Manager on Windows, JP1/IT Desktop Management - Manager on Windows, Job Management Partner 1/IT Desktop Management - Manager on Windows, JP1/NETM/DM Manager on Windows, JP1/NETM/DM Client on Windows, Job Management Partner 1/Software Distribution Manager on Windows, Job Management Partner 1/Software Distribution Client on Windows.This issue affects JP1/IT Desktop Management 2 - Manager: from 13-50 before 13-50-02, from 13-11 before 13-11-04, from 13-10 before 13-10-07, from 13-01 before 13-01-07, from 13-00 before 13-00-05, from 12-60 before 12-60-12, from 10-50 through 12-50-11; JP1/IT Desktop Management 2 - Operations Director: from 13-50 before 13-50-02, from 13-11 before 13-11-04, from 13-10 before 13-10-07, from 13-01 before 13-01-07, from 13-00 before 13-00-05, from 12-60 before 12-60-12, from 10-50 through 12-50-11; Job Management Partner 1/IT Desktop Management 2 - Manager: from 10-50 through 10-50-11; JP1/IT Desktop Management - Manager: from 09-50 through 10-10-16; Job Management Partner 1/IT Desktop Management - Manager: from 09-50 through 10-10-16; JP1/NETM/DM Manager: from 09-00 through 10-20-02; JP1/NETM/DM Client: from 09-00 through 10-20-02; Job Management Partner 1/Software Distribution Manager: from 09-00 through 09-51-13; Job Management Partner 1/Software Distribution Client: from 09-00 through 09-51-13.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: External Control of File Name or Path
The product allows user input to control or influence paths or file names that are used in filesystem operations.
How developers prevent this class of flaw
- When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to inbox.txt and ID 2 could map to profile.txt. Features such as the ESAPI AccessReferenceMap provide this capability.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More External Control of File Name or Path vulnerabilities (CWE-73)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Recent External Control of File Name or Path vulnerabilities
- 8.4 High severity
- 8.4 High severity
- 7.3 High severity
- 8.6 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.