CVE-2025-65115
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRemote 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA critical remote code execution vulnerability exists in multiple Hitachi JP1/IT Desktop Management and Software Distribution products for Windows. The CVSS 9.8 indicates this is network-exploitable with minimal or no authentication required, allowing attackers to execute arbitrary code on affected Windows systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 09-50, <= 09-50-03>= 09-51, <= 09-51-05>= 10-00, <= 10-00-02>= 10-01, <= 10-01-05>= 10-02, <= 10-02-05>= 10-10, <= 10-10-16>= 10-50, <= 10-50-12>= 11-00, <= 11-00-11>= 11-01, <= 11-01-12>= 11-10, <= 11-10-10>= 11-50, <= 11-50-08>= 11-51, <= 11-51-10>= 12-00, <= 12-00-09>= 12-10, <= 12-10-12>= 12-50, <= 12-50-11>= 12-60, <= 12-60-11>= 13-00, <= 13-00-04>= 13-01, <= 13-01-06>= 10-50, <= 10-50-12>= 11-00, <= 11-00-11>= 11-01, <= 11-01-12>= 11-10, <= 11-10-10>= 11-50, <= 11-50-08>= 11-51, <= 11-51-10>= 12-00, <= 12-00-09>= 12-10, <= 12-10-12>= 12-50, <= 12-50-11>= 12-60, <= 12-60-11>= 13-00, <= 13-00-04>= 13-01, <= 13-01-06>= 09-00, <= 09-00-14>= 09-01, <= 09-01-14>= 09-10, <= 09-10-15>= 09-12, <= 09-12-16>= 09-50, <= 09-50-20>= 09-51, <= 09-51-14>= 10-10, <= 10-10-25>= 10-20, <= 10-20-02>= 09-00, <= 09-00-14>= 09-01, <= 09-01-14>= 09-10, <= 09-10-15>= 09-12, <= 09-12-16>= 09-50, <= 09-50-20>= 09-51, <= 09-51-14>= 10-10, <= 10-10-25>= 10-20, <= 10-20-02CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Hitachi JP1 productsOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' to list installed software. Look for products named 'Hitachi JP1', 'Job Management Partner 1', 'it Desktop Management', or 'netm/dm'.Affected if Any of the five affected product families are listed in installed programs.
-
Determine exact version of Hitachi Job Management Partner 1/it Desktop Management ManagerIf installed, check the version through the program entry in Programs and Features, or check the version of the primary executable in the installation directory (typically under C:\Program Files\Hitachi\).Affected if Version falls within any of these ranges: 09-50 to 09-50-03, 09-51 to 09-51-05, 10-00 to 10-00-02, 10-01 to 10-01-05, 10-02 to 10-02-05, or 10-10 to 10-10-16.
-
Determine exact version of Hitachi JP1/it Desktop Management 2 ManagerIf installed, check the version through Programs and Features or the main executable in the installation folder.Affected if Version falls within any of these ranges: 10-50 to 10-50-12, 11-00 to 11-00-11, 11-01 to 11-01-12, 11-10 to 11-10-10, 11-50 to 11-50-08, 11-51 to 11-51-10, 12-00 to 12-00-09, 12-10 to 12-10-12, 12-50 to 12-50-11, 12-60 to 12-60-11, 13-00 to 13-00-04, or 13-01 to 13-01-06.
-
Determine exact version of Hitachi JP1/it Desktop Management 2 Operations DirectorIf installed, check the version through Programs and Features or locate the main executable in the installation directory.Affected if Version falls within any of these ranges: 10-50 to 10-50-12, 11-00 to 11-00-11, 11-01 to 11-01-12, 11-10 to 11-10-10, 11-50 to 11-50-08, 11-51 to 11-51-10, 12-00 to 12-00-09, 12-10 to 12-10-12, 12-50 to 12-50-11, 12-60 to 12-60-11, 13-00 to 13-00-04, or 13-01 to 13-01-06.
-
Determine exact version of Hitachi JP1/netm/dm Manager or ClientIf either product is installed, check the version through Programs and Features or by examining the version of the primary manager or client executable in the installation folder.Affected if Manager version falls within: 09-00 to 09-00-14, 09-01 to 09-01-14, 09-10 to 09-10-15, 09-12 to 09-12-16, 09-50 to 09-50-20, 09-51 to 09-51-14, 10-10 to 10-10-25, or 10-20 to 10-20-02. Client version has the same affected ranges.
The environment is affected if any of the five Hitachi JP1 product families are installed and the installed version falls within the specified version ranges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor-supplied patches to the specific fixed versions (13-50-02, 13-11-04, 13-10-07, 13-01-07, 13-00-05, 12-60-12, 12-50-12, 10-10-17, 10-20-03, 09-51-14 or later) for each affected product line.
Upgrade to the latest fixed version for your product line: JP1/IT Desktop Management 2 to 13-50-02+/12-60-12+, JP1/IT Desktop Management to 10-10-17+, JP1/NETM/DM to 10-20-03+, Job Management Partner 1/Software Distribution to 09-51-14+
- 1. Identify the specific JP1 product and version currently installed from the list of affected products.
- 2. Determine the appropriate fixed version based on the product line: For JP1/IT Desktop Management 2 (Manager/Operations Director): upgrade to 13-50-02, 13-11-04, 13-10-07, 13-01-07, 13-00-05, or 12-60-12 or later. For Job Management Partner 1/IT Desktop Management - Manager: upgrade to 10-10-17 or later. For JP1/NETM/DM (Manager/Client): upgrade to 10-20-03 or later. For Job Management Partner 1
- 3. Obtain the upgrade package from the official Hitachi support portal at www.hitachi.com.
- 4. Before upgrading, backup all critical configuration files and databases as recommended by Hitachi documentation.
- 5. Apply the upgrade following the standard Hitachi JP1 upgrade procedure for your product.
- 6. After upgrade, verify the new version is correctly installed and the service is running.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65115 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data