dbcve.org
Thinkagile Hx5530 FirmwareOperating system · Lenovo

CVE-2023-4606

HIGH · 8.1 CVSS v3.1 Published 2023-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
An authenticated XCC user with Read-Only permission can change a different user’s password through a crafted API command.   This affects ThinkSystem v2 and v3 servers with XCC; ThinkSystem v1 servers are not affected.

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

An authenticated XCC user with Read-Only permission can change a different user's password through a crafted API command, representing a privilege escalation vulnerability due to broken access control in the XCC firmware. This affects ThinkSystem v2 and v3 servers running vulnerable XCC firmware versions.

MitigationApply the latest Lenovo XCC firmware update for ThinkSystem v2 and v3 servers to address the broken access control. Until patched, monitor API activity logs for unauthorized password change attempts and consider restricting API access for Read-Only users.

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
Thinkagile Hx5530 FirmwareOperating system
Affected:all versions
Thinkagile Hx7530 FirmwareOperating system
Affected:all versions
Thinkagile Vx3331 FirmwareOperating system
Affected:all versions
Thinkagile Hx1331 FirmwareOperating system
Affected:all versions
Thinkagile Hx2330 FirmwareOperating system
Affected:all versions
Thinkagile Hx2331 FirmwareOperating system
Affected:all versions
Thinkagile Hx3330 FirmwareOperating system
Affected:all versions
Thinkagile Hx3331 FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 your ThinkSystem server model and firmware version
    Access the XCC (ThinkSystem XClarity Controller) web interface or CLI and locate the firmware version information. Common paths: XCC web UI under 'Firmware Updates' or 'System Information', or via CLI command 'ucsmmget -g firmware'. Compare the XCC firmware version against Lenovo's vulnerability documentation.
    Affected if The server is a Thinkagile Hx5530, Hx7530, Vx3331, Hx1331, Hx2330, Hx2331, Hx3330, or Hx3331 running any XCC firmware version, particularly unpatched versions.
  2. Verify Read-Only users exist in XCC
    In XCC web UI, navigate to 'User Management' or 'Security' settings. Review the list of configured users and their assigned roles. Look for any user accounts with 'Read-Only' or equivalent permission level.
    Affected if At least one Read-Only user account is configured in the XCC user management.
  3. Confirm API access is enabled for Read-Only users
    In XCC settings, check the API configuration or 'External Services' settings. Look for whether the REST API / Redfish API is accessible to Read-Only role users. This may be under 'API Settings' or 'Network Services'.
    Affected if Read-Only users have API access enabled, allowing them to send crafted API commands to the XCC.
  4. Review XCC audit logs for password change activity
    Access XCC audit or event logs through the web UI or via the log export function. Search for 'password change', 'user modification', or API command entries. Look for any password change events initiated by Read-Only users.
    Affected if Logs show password change commands issued by accounts with Read-Only permissions, indicating active exploitation or test attempts.

A user is affected if they operate any of the listed Thinkagile models (Hx5530, Hx7530, Vx3331, Hx1331, Hx2330, Hx2331, Hx3330, Hx3331) with XCC firmware where Read-Only users have API access enabled, as this configuration allows privilege escalation via crafted API password change commands.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest Lenovo XCC firmware update for ThinkSystem v2 and v3 servers to address the broken access control. Until patched, monitor API activity logs for unauthorized password change attempts and consider restricting API access for Read-Only users.

Fix this in Thinkagile Hx5530 Firmware 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-4606 — 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-4606 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