dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2023-6814

MEDIUM · 5.6 CVSS v3.1 Published 2024-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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
Insertion of Sensitive Information into Log File vulnerability in Hitachi Cosminexus Component Container allows local users to gain sensitive information.This issue affects Cosminexus Component Container: from 11-30 before 11-30-05, from 11-20 before 11-20-07, from 11-10 before 11-10-10, from 11-00 before 11-00-12, All versions of V8 and V9.

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

Hitachi Cosminexus Component Container has a log file information disclosure vulnerability where sensitive information is written to log files. Local users with access to the file system can read these logs to obtain sensitive data that should not be exposed.

MitigationApply the vendor-supplied patches to upgrade to version 11-30-05, 11-20-07, 11-10-10, or 11-00-12 or later. For V8/V9 versions without patches, restrict filesystem access to logs and review logging configuration to prevent sensitive data from being written.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/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 if Hitachi Cosminexus Component Container is installed
    Locate the Cosminexus installation directory and look for version information, typically found in product documentation, version files, or the component container's startup scripts
    Affected if The product is present on the system and version is 11-00-12, 11-10-10, 11-20-07, 11-30-05 or earlier
  2. Determine the installed version of Cosminexus Component Container
    Use the vendor-provided version detection method or check the component container's version metadata files if accessible
    Affected if The installed version falls below 11-00-12, 11-10-10, 11-20-07, or 11-30-05 (depending on the product line)
  3. Locate log files generated by the Component Container
    Find log directories used by the Cosminexus Component Container, commonly in the installation logs subdirectory or runtime logs location
    Affected if Log files exist and are accessible to local users beyond the intended administrators
  4. Verify file system permissions on log files
    Check the access control settings on identified log files to determine if non-privileged local users have read access
    Affected if Log files are readable by users other than the administrator or service account that owns them
  5. Inspect log contents for sensitive information
    Examine the log files for patterns indicating sensitive data such as credentials, tokens, personal information, or session data that should not be recorded
    Affected if Log files contain any sensitive information that should not have been written to disk

You are affected if Hitachi Cosminexus Component Container is installed with a version earlier than 11-00-12, 11-10-10, 11-20-07, or 11-30-05 and its log files contain sensitive information accessible to local users.

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 the vendor-supplied patches to upgrade to version 11-30-05, 11-20-07, 11-10-10, or 11-00-12 or later. For V8/V9 versions without patches, restrict filesystem access to logs and review logging configuration to prevent sensitive data from being written.

Recommended fix High confidence

11-30-05 or later (for 11-30 branch), 11-20-07 or later (for 11-20 branch), 11-10-10 or later (for 11-10 branch), 11-00-12 or later (for 11-00 branch)

  1. Identify your current Cosminexus Component Container version by checking the product version
  2. If running version 11-30.x, upgrade to version 11-30-05 or later
  3. If running version 11-20.x, upgrade to version 11-20-07 or later
  4. If running version 11-10.x, upgrade to version 11-10-10 or later
  5. If running version 11-00.x, upgrade to version 11-00-12 or later
  6. For V8 and V9 versions, contact Hitachi support for available patches or consider migrating to a supported version (V11)
  7. After upgrade, verify that sensitive information is no longer being written to log files
Caveat Standard upgrade precautions apply - test in non-production environment before deploying to production

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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