CVE-2025-65116
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 · uneditedBuffer Overflow 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 · high confidenceA buffer overflow vulnerability exists in multiple JP1/IT Desktop Management and related software products for Windows. The vulnerability has a CVSS score of 5.5 (MEDIUM), indicating it could allow an attacker to cause a denial of service or potentially execute arbitrary code by overflowing a memory buffer in the affected application components.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 JP1 productCheck the Windows system for installed Hitachi JP1/IT Desktop Management or JP1/NETM/DM software via Windows Programs and Features (Add/Remove Programs), or look for product-specific folders in Program Files such as 'Hitachi' or 'JP1' directories.Affected if Any of the following products are installed: JP1/IT Desktop Management Manager, JP1/IT Desktop Management 2 Manager, JP1/IT Desktop Management 2 Operations Director, JP1/NETM/DM Manager, or JP1/NETM/DM Client.
-
Retrieve installed version numberIn Windows Programs and Features, locate the Hitachi JP1 product entry and note the exact version number shown in the Version column, or right-click the product and select Properties to view the version details.Affected if The installed version matches any of the affected version ranges specified in the CVE (e.g., 09-50 through 09-50-03, 10-10 through 10-10-16 for JP1/IT Desktop Management Manager; 10-50 through 10-50-12 for JP1/IT Desktop Management 2; 09-00 through 09-00-14 for JP1/NETM/DM).
-
Cross-reference version against CVE rangesCompare the retrieved version number against the affected version ranges provided in the CVE. Use the full version string including any build or revision numbers (e.g., 10-10-16 includes the '-16' suffix).Affected if The installed version falls within any of the specified vulnerable ranges and is not one of the patched versions (13-50-02, 13-11-04, 13-10-07, 13-01-07, 13-00-05, 12-60-12, 10-10-17, 10-20-03, 09-51-14).
-
Verify product component is runningCheck running processes in Windows Task Manager for JP1-related services or executables. Look for processes with names containing 'jp1', 'netm', 'dm', or 'Desktop Management' in the process list.Affected if The vulnerable product component is actively running on the system, which would allow the buffer overflow to be triggered.
A user is affected if any of the listed JP1/IT Desktop Management or JP1/NETM/DM products are installed with versions matching the affected ranges and the component is operational.
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 for the specific affected versions of each product. Upgrade to the patched versions: JP1/IT Desktop Management 2 to 13-50-02/13-11-04/13-10-07/13-01-07/13-00-05/12-60-12 or later; JP1/IT Desktop Management to 10-10-17 or later; JP1/NETM/DM to 10-20-03 or later; and Job Management Partner 1/Software Distribution to 09-51-14 or later.
Upgrade to the latest version in your release branch (e.g., 13-50-02, 12-60-12, 10-50-12, 10-10-16, 10-20-02, or 09-51-13 depending on product line)
- 1. Identify the exact product and current version of JP1/IT Desktop Management software installed using system inventory or product documentation.
- 2. For JP1/IT Desktop Management 2 - Manager: upgrade to version 13-50-02, 13-11-04, 13-10-07, 13-01-07, 13-00-05, or 12-60-12 (whichever is applicable to your release line).
- 3. For JP1/IT Desktop Management 2 - Operations Director: upgrade to version 13-50-02, 13-11-04, 13-10-07, 13-01-07, 13-00-05, or 12-60-12 (whichever is applicable to your release line).
- 4. For Job Management Partner 1/IT Desktop Management 2 - Manager: upgrade to version 10-50-12 or later.
- 5. For JP1/IT Desktop Management - Manager or Job Management Partner 1/IT Desktop Management - Manager: upgrade to version 10-10-16 or later.
- 6. For JP1/NETM/DM Manager or JP1/NETM/DM Client: upgrade to version 10-20-02 or later.
- 7. For Job Management Partner 1/Software Distribution Manager or Client: upgrade to version 09-51-13 or later.
- 8. Obtain the fixed version from official Hitachi channels (Hitachi Support Portal or your Hitachi account representative).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65116 — 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-65116 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