dbcve.org
Jp1\/performance ManagementApplication · Hitachi

CVE-2023-3440

HIGH · 7.8 CVSS v3.1 Published 2023-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Incorrect Default Permissions vulnerability in Hitachi JP1/Performance Management on Windows allows File Manipulation.This issue affects JP1/Performance Management - Manager: from 09-00 before 12-50-07; JP1/Performance Management - Base: from 09-00 through 10-50-*; JP1/Performance Management - Agent Option for Application Server: from 11-00 before 11-50-16; JP1/Performance Management - Agent Option for Enterprise Applications: from 09-00 before 12-00-14; JP1/Performance Management - Agent Option for HiRDB: from 09-00 before 12-00-14; JP1/Performance Management - Agent Option for IBM Lotus Domino: from 10-00 before 11-50-16; JP1/Performance Management - Agent Option for Microsoft(R) Exchange Server: from 09-00 before  12-00-14; JP1/Performance Management - Agent Option for Microsoft(R) Internet Information Server: from 09-00 before 12-00-14; JP1/Performance Management - Agent Option for Microsoft(R) SQL Server: from 09-00 before 12-50-07; JP1/Performance Management - Agent Option for Oracle: from 09-00 before  12-10-08; JP1/Performance Management - Agent Option for Platform: from 09-00 before 12-50-07; JP1/Performance Management - Agent Option for Service Response: from 09-00 before 11-50-16; JP1/Performance Management - Agent Option for Transaction System: from 11-00 before 12-00-14; JP1/Performance Management - Remote Monitor for Microsoft(R) SQL Server: from 09-00 before 12-50-07; JP1/Performance Management - Remote Monitor for Oracle: from 09-00 before 12-10-08; JP1/Performance Management - Remote Monitor for Platform: from 09-00 before 12-10-08; JP1/Performance Management - Remote Monitor for Virtual Machine: from 10-00 before 12-50-07; JP1/Performance Management - Agent Option for Domino: from 09-00 through 09-00-*; JP1/Performance Management - Agent Option for IBM WebSphere Application Server: from 09-00 through 10-00-*; JP1/Performance Management - Agent Option for IBM WebSphere MQ: from 09-00 through 10-00-*; JP1/Performance Management - Agent Option for JP1/AJS3: from 09-00 through 10-00-*; JP1/Performance Management - Agent Option for OpenTP1: from 09-00 through 10-00-*; JP1/Performance Management - Agent Option for Oracle WebLogic Server: from 09-00 through 10-00-*; JP1/Performance Management - Agent Option for uCosminexus Application Server: from 09-00 through 10-00-*; JP1/Performance Management - Agent Option for Virtual Machine: from 09-00 through 09-01-*.

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 confidence

Incorrect default file permissions in Hitachi JP1/Performance Management on Windows allow local attackers to manipulate files they should not have access to. The vulnerability stems from overly permissive default ACLs on certain files or directories, enabling privilege escalation via file modification or replacement.

MitigationApply vendor-supplied patches to upgrade affected components to the fixed versions (e.g., Manager to 12-50-07, Base to 11-00 or later, Agent Options to their respective fixed releases). Review and harden file system permissions on JP1 installation directories as an interim measure.

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
Jp1\/performance ManagementApplication
Affected:all versions

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if JP1/Performance Management is installed
    Look for the JP1 installation directory in common locations such as C:\Program Files\Hitachi\JP1, C:\Hitachi\JP1, or check Windows Registry under HKLM\SOFTWARE\Hitachi for JP1 installation entries
    Affected if The product is found installed on the system
  2. Identify the JP1 installation root directory
    Locate the main JP1 installation folder (commonly under Program Files\Hitachi or a custom path configured during installation)
    Affected if The installation directory exists and contains JP1 components
  3. Review file permissions on the JP1 installation directory
    Right-click the JP1 root folder, select Properties, go to the Security tab, and examine the granted permissions for each user or group
    Affected if ACLs grant excessive permissions to non-admin users (such as Everyone, Users, or Authenticated Users having Write or Modify access to sensitive directories)
  4. Inspect permissions on JP1 configuration and executable directories
    Check ACLs on subdirectories containing configuration files (.conf, .ini, .xml) and executable files (.exe, .dll) within the JP1 installation folder
    Affected if Non-privileged users or groups have Write or Modify permissions on config or binary directories that should be restricted to administrators only
  5. Verify if default permissions allow file modification by low-privileged accounts
    Using icacls.exe from a limited user account context, attempt to list or modify files in the JP1 installation directory to confirm overly permissive access
    Affected if A standard user account can successfully write, modify, or replace files in directories that should be protected

If Hitachi JP1/Performance Management is installed and the default ACLs on its installation directories grant Write or Modify access to non-administrative users or groups, the environment is affected by CVE-2023-3440.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches to upgrade affected components to the fixed versions (e.g., Manager to 12-50-07, Base to 11-00 or later, Agent Options to their respective fixed releases). Review and harden file system permissions on JP1 installation directories as an interim measure.

Recommended fix Moderate confidence

JP1/Performance Management - Manager: 12-50-07 or later; Base: 10-51 or later; respective Agent Options and Remote Monitors at or above their respective threshold versions (e.g., 12-50-07, 12-10-08, 11-50-16, 12-00-14 as indicated by 'before' in version ranges)

  1. Contact Hitachi support to obtain the specific patch or updated version for your JP1/Performance Management product line
  2. Request the fixed versions: JP1/Performance Management - Manager 12-50-07 or later; Base 10-51 or later; Agent Options and Remote Monitors according to the thresholds in the advisory
  3. Test the updated version in a non-production environment before deploying
  4. Apply the update following Hitachi's standard upgrade procedures for JP1/Performance Management
Caveat Review Hitachi's release notes for the target version to check for any compatibility or configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jp1\/performance Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3440 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3440 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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