dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-68919

MEDIUM · 5.6 CVSS v3.1 Published 2025-12-24
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
Fujitsu / Fsas Technologies ETERNUS SF ACM/SC/Express (DX / AF Management Software) before 16.8-16.9.1 PA 2025-12, when collected maintenance data is accessible by a principal/authority other than ETERNUS SF Admin, allows an attacker to potentially affect system confidentiality, integrity, and availability.

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

This is an improper access control vulnerability in Fujitsu ETERNUS SF storage management software where collected maintenance data is accessible to principals/authorities other than the intended ETERNUS SF Admin role. An attacker with access to these alternative authorization paths could potentially read, modify, or disrupt maintenance data, affecting confidentiality, integrity, and availability.

MitigationUpgrade to ETERNUS SF ACM/SC/Express version 16.8-16.9.1 PA 2025-12 or later, which contains the access control fix for this vulnerability.

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 ETERNUS SF is installed
    Locate the ETERNUS SF installation directory or check for the presence of ETERNUS SF components on the system. Common installation paths may include /opt/fujitsu/eternus or C:\Program Files\Fujitsu\ETERNUS on Windows.
    Affected if ETERNUS SF software is found on the system
  2. Determine the installed ETERNUS SF version
    Use the product's version checking mechanism - typically via the management console, about dialog, or version command. Look for version information in the format such as 16.x or check the software package details.
    Affected if The installed version falls within 16.8 through 16.9.1 PA 2025-12 (versions prior to the December 2025 patch)
  3. Review maintenance data access configurations
    Examine the access control settings for maintenance data collection features. Look for configuration files or settings that define who can access collected maintenance data and verify if non-admin roles have been granted access permissions.
    Affected if Non-admin users or roles have permissions to access maintenance data collections
  4. Check for alternative authorization paths
    Inspect the system's role-based access control (RBAC) configuration to identify any authorization paths that allow access to maintenance data outside of the intended ETERNUS SF Admin role.
    Affected if Authorization paths exist that grant maintenance data access to users without the ETERNUS SF Admin role

A user is affected if they have ETERNUS SF version 16.8 through 16.9.1 PA 2025-12 installed AND maintenance data is accessible to principals other than the ETERNUS SF Admin role.

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

Upgrade to ETERNUS SF ACM/SC/Express version 16.8-16.9.1 PA 2025-12 or later, which contains the access control fix for this vulnerability.

Recommended fix Moderate confidence

16.8-16.9.1 PA 2025-12 or later

  1. 1. Identify the current installed version of Fujitsu ETERNUS SF ACM/SC/Express (DX / AF Management Software)
  2. 2. Schedule a maintenance window for the upgrade procedure
  3. 3. Backup all current configurations and data according to Fujitsu backup procedures
  4. 4. Obtain the upgrade package for version 16.8-16.9.1 PA 2025-12 or later from Fujitsu's official support channels
  5. 5. Follow the official Fujitsu upgrade documentation for your specific product (ETERNUS SF ACM, SC, or Express)
  6. 6. Verify the upgrade was successful by checking the version number in the management interface
  7. 7. Confirm that maintenance data access controls are properly configured post-upgrade
Caveat Review Fujitsu release notes for any configuration changes or compatibility considerations between your current version and 16.8-16.9.1 PA 2025-12

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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