Insufficient Logging Vulnerability in HiRDB
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Hitachi HiRDB Server 09-60-39, 09-65-23, 09-66-17; Hitachi HiRDB Server With Addtional Function 09-60-2M, 09-65-/W, 09-66-/Q; Hitachi HiRDB Structured Data Access Facility 09-60-39, 10-03-12, 10-04-06.
- Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 7.5.
Low priority for now. Upgrade to Hitachi HiRDB Server 09-60-39, 09-65-23, 09-66-17; Hitachi HiRDB Server With Addtional Function 09-60-2M, 09-65-/W, 09-66-/Q; Hitachi HiRDB Structured Data Access Facility 09-60-39, 10-03-12, 10-04-06 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 28, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-778
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · Hitachi
- 5.3
- 2.2 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hitachi | hirdb server with additional function | cpe:2.3:a:hitachi:hirdb_server_with_additional_function |
| hitachi | hirdb structured data access facility | cpe:2.3:a:hitachi:hirdb_structured_data_access_facility |
| hitachi | hirdb server | cpe:2.3:a:hitachi:hirdb_server |
| hp | hp-ux | cpe:2.3:o:hp:hp-ux |
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
| ibm | aix | cpe:2.3:o:ibm:aix |
| oracle | solaris | cpe:2.3:o:oracle:solaris |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hitachi hirdb server09-60 and later · up to 09-60-37 inclusive
- hitachi hirdb server09-02 and later · up to 09-02-32 inclusive
- hitachi hirdb server09-03 and later · up to 09-03-27 inclusive
- hitachi hirdb server09-04 and later · up to 09-04-31 inclusive
- hitachi hirdb server09-00 and later · up to 09-00-32 inclusive
- hitachi hirdb server09-03 and later · up to 09-03-31 inclusive
- hitachi hirdb server09-04 and later · up to 09-04-45 inclusive
- hitachi hirdb server09-50 and later · up to 09-50-37 inclusive
- hitachi hirdb server09-60 and later · up to 09-60-38 inclusive
- hitachi hirdb server09-65 and later · up to 09-65-22 inclusive
- hitachi hirdb server09-66 and later · up to 09-66-16 inclusive
- hitachi hirdb server10-00 and later · up to 10-00-09 inclusive
- hitachi hirdb server10-01 and later · up to 10-01-09 inclusive
- hitachi hirdb server10-02 and later · up to 10-02-12 inclusive
- hitachi hirdb server10-03 and later · up to 10-03-11 inclusive
- hitachi hirdb server10-04 and later · up to 10-04-04 inclusive
- hitachi hirdb server10-05 and later · up to 10-05-05 inclusive
- hitachi hirdb server10-06 and later · up to 10-06-01 inclusive
- hitachi hirdb server10-03 and later · up to 10-03-10 inclusive
- hitachi hirdb server10-04 and later · up to 10-04-05 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Hitachi). Independent of NVD's CPE analysis and usually ahead of it.
Hitachi HiRDB Server
- 07-03 and later · before 09-60affected
- 09-60 and later · before 09-60-39affectedfixed in 09-60-39
- 09-65 and later · before 09-65-23affectedfixed in 09-65-23
- 09-66 and later · before 09-66-17affectedfixed in 09-66-17
- 10-00 and later · up to and including 10-00-*affected
- 10-01 and later · before 10-01-10affectedfixed in 10-01-10
- 10-02 and later · up to and including 10-02-*affected
- 10-03 and later · before 10-03-12affectedfixed in 10-03-12
- 10-04 and later · before 10-04-06affectedfixed in 10-04-06
- 10-05 and later · before 10-05-06affectedfixed in 10-05-06
Hitachi HiRDB Server With Addtional Function
- 07-03 and later · before 09-60affected
- 09-60 and later · before 09-60-2Maffectedfixed in 09-60-2M
- 09-65 and later · before 09-65-/Waffectedfixed in 09-65-/W
- 09-66 and later · before 09-66-/Qaffectedfixed in 09-66-/Q
Hitachi HiRDB Structured Data Access Facility
- 07-03 and later · before 09-60affected
- 09-60 and later · before 09-60-39affectedfixed in 09-60-39
- 09-65 and later · up to and including 09-65-*affected
- 09-66 and later · up to and including 09-66-*affected
- 10-00 and later · up to and including 10-00-*affected
- 10-01 and later · up to and including 10-01-*affected
- 10-02 and later · up to and including 10-02-*affected
- 10-03 and later · before 10-03-12affectedfixed in 10-03-12
- 10-04 and later · before 10-04-06affectedfixed in 10-04-06
- 10-05 and later · up to and including 10-05-*affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Hitachi HiRDB Server | 09-60-39 | Vendor (CNA) |
| Hitachi HiRDB Server | 09-65-23 | Vendor (CNA) |
| Hitachi HiRDB Server | 09-66-17 | Vendor (CNA) |
| Hitachi HiRDB Server | 10-01-10 | Vendor (CNA) |
| Hitachi HiRDB Server | 10-03-12 | Vendor (CNA) |
| Hitachi HiRDB Server | 10-04-06 | Vendor (CNA) |
| Hitachi HiRDB Server | 10-05-06 | Vendor (CNA) |
| Hitachi HiRDB Server | 10-06-02 | Vendor (CNA) |
| Hitachi HiRDB Server With Addtional Function | 09-60-2M | Vendor (CNA) |
| Hitachi HiRDB Server With Addtional Function | 09-65-/W | Vendor (CNA) |
| Hitachi HiRDB Server With Addtional Function | 09-66-/Q | Vendor (CNA) |
| Hitachi HiRDB Structured Data Access Facility | 09-60-39 | Vendor (CNA) |
| Hitachi HiRDB Structured Data Access Facility | 10-03-12 | Vendor (CNA) |
| Hitachi HiRDB Structured Data Access Facility | 10-04-06 | Vendor (CNA) |
| Hitachi HiRDB Structured Data Access Facility | 10-06-02 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-778 · Insufficient LoggingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.