HiRDB Server: Insufficient Logging
CVE-2023-1995 is a high-severity insufficient logging vulnerability in HiRDB Server from Hitachi, with a CVSS 3.1 base score of 7.5 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 09-60, 09-60-39, 09-65-23 as the first without the flaw, so updating HiRDB Server to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.46% 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 HiRDB Server to 09-60 or 09-60-39 or 09-65-23 or 09-66-17, whichever matches your release line, or a later version.
- Update HiRDB Server With Addtional Function to 09-60 or 09-60-2M or 09-65-/W or 09-66-/Q, whichever matches your release line, or a later version.
- Update HiRDB Structured Data Access Facility to 09-60 or 09-60-39 or 10-03-12 or 10-04-06, 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 | HiRDB Server | 07-03 up to, but not including, 09-60; 09-60 up to, but not including, 09-60-39; 09-65 up to, but not including, 09-65-23; 09-66 up to, but not including, 09-66-17; 10-00 through 10-00-*; 10-01 up to, but not including, 10-01-10; 10-02 through 10-02-*; 10-03 up to, but not including, 10-03-12; and 3 more ranges | 09-60, 09-60-39, 09-65-23, 09-66-17, 10-01-10, 10-03-12 |
| Hitachi | HiRDB Server With Addtional Function | 07-03 up to, but not including, 09-60; 09-60 up to, but not including, 09-60-2M; 09-65 up to, but not including, 09-65-/W; 09-66 up to, but not including, 09-66-/Q | 09-60, 09-60-2M, 09-65-/W, 09-66-/Q |
| Hitachi | HiRDB Structured Data Access Facility | 07-03 up to, but not including, 09-60; 09-60 up to, but not including, 09-60-39; 09-65 through 09-65-*; 09-66 through 09-66-*; 10-00 through 10-00-*; 10-01 through 10-01-*; 10-02 through 10-02-*; 10-03 up to, but not including, 10-03-12; and 3 more ranges | 09-60, 09-60-39, 10-03-12, 10-04-06, 10-06-02 |
| Hitachi | Hirdb Server With Additional Function | 09-00 through 09-00-2d; 09-01 through 09-01-\/x; 09-02 through 09-02-2f; 09-03 through 09-03-2a; 09-04 through 09-04-2s; 09-50 through 09-50-2k; 09-60 through 09-60-2k; 09-65 through 09-65-\/v; and 4 more ranges | 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
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.3 | Medium | CNA (hitachi.co.jp) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
Insufficient Logging vulnerability in Hitachi HiRDB Server, HiRDB Server With Addtional Function, HiRDB Structured Data Access Facility.This issue affects HiRDB Server: before 09-60-39, before 09-65-23, before 09-66-17, before 10-01-10, before 10-03-12, before 10-04-06, before 10-05-06, before 10-06-02; HiRDB Server With Addtional Function: before 09-60-2M, before 09-65-/W , before 09-66-/Q ; HiRDB Structured Data Access Facility: before 09-60-39, before 10-03-12, before 10-04-06, before 10-06-02.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insufficient Logging
When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.
How developers prevent this class of flaw
- Use a centralized logging mechanism that supports multiple levels of detail.
- Ensure that all security-related successes and failures can be logged. When storing data in the cloud (e.g., AWS S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to enable and capture detailed logging information.
- Be sure to set the level of logging appropriately in a production environment. Sufficient data should be logged to enable system administrators to detect attacks, diagnose errors, and recover from attacks. At the same time, logging too much data (CWE-779) can cause the same problems, including unexpected costs when using a cloud environment.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Spotted an error? Tell us.