dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-65002

HIGH · 7.5 CVSS v3.1 Published 2025-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 iRMC S6 on M5 before 1.37S mishandles Redfish/WebUI access if the length of a username is exactly 16 characters.

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

Fujitsu iRMC S6 on M5 servers before version 1.37S contains an access control vulnerability where the system mishandles Redfish/WebUI authentication when a username length is exactly 16 characters, potentially allowing unauthorized access.

MitigationUpgrade Fujitsu iRMC S6 firmware to version 1.37S or later. Until patched, restrict network access to the management interface to trusted networks only.

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

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

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 the iRMC firmware version
    Access the Fujitsu iRMC web interface (WebUI) or use Redfish API to retrieve the firmware version. In the WebUI, navigate to 'Maintenance' or 'Firmware Information'. Via Redfish, use GET /redfish/v1/Managers/1 or similar endpoint to query the firmware version.
    Affected if The installed firmware version is below 1.37S (e.g., 1.36P, 1.35X, etc.)
  2. Confirm the server model is M5
    Check the server model through the iRMC web interface under 'System' or 'ServerView', or via Redfish at /redfish/v1/Systems/1. Verify it is a Fujitsu M5 series server.
    Affected if The server is a Fujitsu M5 model running an affected iRMC S6 firmware version before 1.37S
  3. Verify WebUI interface is accessible
    Attempt to reach the iRMC WebUI at https://<ip-address>/ - confirm the interface is reachable and not disabled.
    Affected if The WebUI is enabled and accessible on the network (this interface is where the authentication flaw occurs)
  4. Verify Redfish API is accessible
    Test connectivity to the Redfish endpoint at https://<ip-address>/redfish/v1/ - confirm it responds.
    Affected if The Redfish API is enabled and accessible (this interface is where the authentication flaw occurs)
  5. Check for 16-character usernames
    List user accounts in the iRMC under 'User Management' or via Redfish at /redfish/v1/AccountService/Accounts . Count the character length of each username.
    Affected if Any user account exists with a username that is exactly 16 characters long

A user is affected if they are running Fujitsu iRMC S6 firmware before version 1.37S on an M5 server with WebUI or Redfish accessible, and have at least one user account with a 16-character username.

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 Fujitsu iRMC S6 firmware to version 1.37S or later. Until patched, restrict network access to the management interface to trusted networks only.

Recommended fix Moderate confidence

1.37S or later

  1. Identify the current firmware version of the Fujitsu iRMC S6 by accessing the WebUI or via Redfish API
  2. Download the firmware version 1.37S or later from Fujitsu's support portal
  3. Upload the firmware through the iRMC WebUI interface (typically under Maintenance > Firmware Update) or via Redfish UpdateService
  4. Verify the firmware update was successful and the system is operational
  5. Confirm the vulnerability is remediated by testing Redfish/WebUI access with a 16-character username

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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