dbcve.org
Hirdb Server With Additional FunctionApplication · Hitachi

CVE-2023-1995

HIGH · 7.5 CVSS v3.1 Published 2023-08-29
Fix available
A fix is available. Upgrade to after 10-06-01 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
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.

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 confidence

Insufficient Logging vulnerability in Hitachi HiRDB Server and related components means the database system fails to adequately log security-relevant events such as authentication attempts, privileged operations, or data access. This can allow attackers to operate undetected and impedes forensic investigation. The CVSS 7.5 score indicates this insufficient logging has significant security impact.

MitigationApply the vendor patches to update HiRDB Server to versions 09-60-39 or later (for 09-x branches), 10-01-10 or later, 10-03-12 or later, 10-04-06 or later, 10-05-06 or later, and 10-06-02 or later depending on the branch; also update HiRDB Server With Additional Function and HiRDB Structured Data Access Facility to their patched versions.

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
Hirdb Server With Additional FunctionApplication
Affected:>= 09-00, <= 09-00-2d>= 09-01, <= 09-01-\/x>= 09-02, <= 09-02-2f>= 09-03, <= 09-03-2a>= 09-04, <= 09-04-2s>= 09-50, <= 09-50-2k>= 09-60, <= 09-60-2k>= 09-65, <= 09-65-\/v>= 09-66, <= 09-66-\/p>= 09-00, <= 09-00-2f>= 09-03, <= 09-03-2e>= 09-60, <= 09-60-2l
Hirdb Structured Data Access FacilityApplication
Affected:>= 09-60, <= 09-60-37>= 09-66, <= 09-66-06>= 10-01, <= 10-01-03>= 10-02, <= 10-02-12>= 10-03, <= 10-03-10>= 10-04, <= 10-04-05>= 10-06, <= 10-06-01
Hirdb ServerApplication
Affected:>= 09-00, <= 09-00-30>= 09-01, <= 09-01-24>= 09-02, <= 09-02-32>= 09-03, <= 09-03-27>= 09-04, <= 09-04-31>= 09-00, <= 09-00-32>= 09-03, <= 09-03-31>= 09-04, <= 09-04-45>= 09-50, <= 09-50-37>= 09-60, <= 09-60-38>= 09-65, <= 09-65-22>= 09-66, <= 09-66-16

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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. Identify HiRDB Server version
    Run the pdversion command or query the system catalog (e.g., SELECT * FROM VERSION) to obtain the installed HiRDB Server version number
    Affected if The version falls within any of the affected ranges listed in the CVE for HiRDB Server, HiRDB Server With Additional Function, or HiRDB Structured Data Access Facility
  2. Identify HiRDB Structured Data Access Facility version
    Check the installed version of the HiRDB Structured Data Access Facility component if deployed, using its specific version query method or check installed packages
    Affected if The version falls within the affected ranges for HiRDB Structured Data Access Facility (09-60 to 09-60-37, 09-66 to 09-66-06, 10-01 to 10-01-03, 10-02 to 10-02-12, 10-03 to 10-03-10, 10-04 to 10-04-05, or 10-06 to 10-06-01)
  3. Identify HiRDB Server With Additional Function version
    Check the installed version of the HiRDB Server With Additional Function component if deployed, using its specific version query method or check installed packages
    Affected if The version falls within any of the affected ranges listed for HiRDB Server With Additional Function
  4. Verify audit logging configuration
    Examine the HiRDB audit log configuration files or settings (typically managed via pdmkracl or similar audit configuration tools) to determine whether security-relevant events such as authentication attempts, privileged operations, and data access are being logged
    Affected if Audit logging is disabled, not configured, or configured to omit authentication attempts, privileged operations, or data access events

You are affected if your installed HiRDB Server, HiRDB Server With Additional Function, or HiRDB Structured Data Access Facility version falls within any of the CVE-affected ranges AND audit logging for security events is not properly configured.

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
Upgrade available Upgrade to a release after 10-06-01
Interim mitigation

Apply the vendor patches to update HiRDB Server to versions 09-60-39 or later (for 09-x branches), 10-01-10 or later, 10-03-12 or later, 10-04-06 or later, 10-05-06 or later, and 10-06-02 or later depending on the branch; also update HiRDB Server With Additional Function and HiRDB Structured Data Access Facility to their patched versions.

Recommended fix High confidence

HiRDB Server: upgrade to 10-06-02 or later; HiRDB Structured Data Access Facility: upgrade to 10-06-02 or later; HiRDB Server With Additional Function: upgrade to latest available fixed version per Hitachi advisory

  1. 1. Identify the current installed version of Hitachi HiRDB (Server, Server With Additional Function, or Structured Data Access Facility)
  2. 2. Determine which product and version family applies to your installation
  3. 3. For HiRDB Server: upgrade to version 09-60-39 or later (09-65-23+, 09-66-17+, 10-01-10+, 10-03-12+, 10-04-06+, or 10-06-02+)
  4. 4. For HiRDB Structured Data Access Facility: upgrade to version 09-60-39 or later (10-03-12+, 10-04-06+, or 10-06-02+)
  5. 5. For HiRDB Server With Additional Function: upgrade to the equivalent fixed version as listed in Hitachi advisories
  6. 6. Verify the fix by checking that insufficient logging has been addressed in release notes
  7. 7. Test the upgraded system in a non-production environment before deploying to production
Caveat Review Hitachi release notes for migration considerations between major version jumps (e.g., 09-xx to 10-xx)

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

Fix this in Hirdb Server With Additional Function Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1995 — 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-1995 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