JP1/Performance Management - Manager: Incorrect Default Permissions
CVE-2023-3440 is a high-severity incorrect default permissions vulnerability in JP1/Performance Management - Manager from Hitachi, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 11-50, 11-50-16, 12-00-14 as the first without the flaw, so updating JP1/Performance Management - Manager to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.2% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update JP1/Performance Management - Manager to 11-50 or 11-50-16 or 12-00-14 or 12-10-08, whichever matches your release line, or a later version.
- Update JP1/Performance Management - Agent Option for Application Server to 11-50-16 or a later version.
- Update JP1/Performance Management - Agent Option for Enterprise Applications to 11-50 or 11-50-16 or 12-00-14, whichever matches your release line, or a later version.
- Read the advisory on hitachi.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Hitachi | JP1/Performance Management - Manager | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14; 12-10 up to, but not including, 12-10-08; 12-50 up to, but not including, 12-50-07 | 11-50, 11-50-16, 12-00-14, 12-10-08, 12-50-07 |
| Hitachi | JP1/Performance Management - Base | 09-00 through 10-50-* | Not stated |
| Hitachi | JP1/Performance Management - Agent Option for Application Server | 11-00 up to, but not including, 11-50-16 | 11-50-16 |
| Hitachi | JP1/Performance Management - Agent Option for Enterprise Applications | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14 | 11-50, 11-50-16, 12-00-14 |
| Hitachi | JP1/Performance Management - Agent Option for HiRDB | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14 | 11-50, 11-50-16, 12-00-14 |
| Hitachi | JP1/Performance Management - Agent Option for IBM Lotus Domino | 10-00 up to, but not including, 11-50-16 | 11-50-16 |
| Hitachi | JP1/Performance Management - Agent Option for Microsoft(R) Exchange Server | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14 | 11-50, 11-50-16, 12-00-14 |
| Hitachi | JP1/Performance Management - Agent Option for Microsoft(R) Internet Information Server | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14 | 11-50, 11-50-16, 12-00-14 |
| Hitachi | JP1/Performance Management - Agent Option for Microsoft(R) SQL Server | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14; 12-50 up to, but not including, 12-50-07 | 11-50, 11-50-16, 12-00-14, 12-50-07 |
| Hitachi | JP1/Performance Management - Agent Option for Oracle | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14; 12-10 up to, but not including, 12-10-08 | 11-50, 11-50-16, 12-00-14, 12-10-08 |
| Hitachi | JP1/Performance Management - Agent Option for Platform | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14; 12-50 up to, but not including, 12-50-07 | 11-50, 11-50-16, 12-00-14, 12-50-07 |
| Hitachi | JP1/Performance Management - Agent Option for Service Response | 09-00 up to, but not including, 11-50-16 | 11-50-16 |
| Hitachi | JP1/Performance Management - Agent Option for Transaction System | 11-00 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14 | 11-50-16, 12-00-14 |
| Hitachi | JP1/Performance Management - Remote Monitor for Microsoft(R) SQL Server | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14; 12-50 up to, but not including, 12-50-07 | 11-50, 11-50-16, 12-00-14, 12-50-07 |
| Hitachi | JP1/Performance Management - Remote Monitor for Oracle | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14; 12-10 up to, but not including, 12-10-08 | 11-50, 11-50-16, 12-00-14, 12-10-08 |
| Hitachi | JP1/Performance Management - Remote Monitor for Platform | 09-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14; 12-10 up to, but not including, 12-10-08 | 11-50, 11-50-16, 12-00-14, 12-10-08 |
| Hitachi | JP1/Performance Management - Remote Monitor for Virtual Machine | 10-00 up to, but not including, 11-50; 11-50 up to, but not including, 11-50-16; 12-00 up to, but not including, 12-00-14; 12-10 up to, but not including, 12-10-08; 12-50 up to, but not including, 12-50-07 | 11-50, 11-50-16, 12-00-14, 12-10-08, 12-50-07 |
| Hitachi | JP1/Performance Management - Agent Option for Domino | 09-00 through 09-00-* | Not stated |
| Hitachi | JP1/Performance Management - Agent Option for IBM WebSphere Application Server | 09-00 through 10-00-* | Not stated |
| Hitachi | JP1/Performance Management - Agent Option for IBM WebSphere MQ | 09-00 through 10-00-* | Not stated |
| Hitachi | JP1/Performance Management - Agent Option for JP1/AJS3 | 09-00 through 10-00-* | Not stated |
| Hitachi | JP1/Performance Management - Agent Option for OpenTP1 | 09-00 through 10-00-* | Not stated |
| Hitachi | JP1/Performance Management - Agent Option for Oracle WebLogic Server | 09-00 through 10-00-* | Not stated |
| Hitachi | JP1/Performance Management - Agent Option for uCosminexus Application Server | 09-00 through 10-00-* | Not stated |
| Hitachi | JP1/Performance Management - Agent Option for Virtual Machine | 09-00 through 09-01-* | Not stated |
Version data comes from the organisation that assigned the CVE; 1 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.4 | High | CNA (hitachi.co.jp) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
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-*.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Default Permissions
During installation, installed file permissions are set to allow anyone to modify those files.
How developers prevent this class of flaw
- The architecture needs to access and modification attributes for files to only those users who actually require those actions.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
More Incorrect Default Permissions vulnerabilities (CWE-276)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Recent Incorrect Default Permissions vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.8 High severity
Spotted an error? Tell us.