dbcve.org
Thinkagile Hx5530 FirmwareOperating system · Lenovo

CVE-2023-25492

HIGH · 8.8 CVSS v3.1 Published 2023-05-01
Fix available
A fix is available. Upgrade to 2.93_afbt30p / 3.72_tei388s or later.
See remediation →
94/100
Remediation priority · Urgent
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
A valid, authenticated user may be able to trigger a denial of service of the XCC web user interface or other undefined behavior through a format string injection vulnerability in a web interface API.

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 a format string injection vulnerability in the XCC web interface API. An authenticated user can inject format string specifiers (such as %s, %n, %x) into API input parameters, which the underlying code incorrectly processes as format string arguments instead of literal strings. This can cause the application to crash (denial of service) or execute arbitrary code (undefined behavior).

MitigationImplement strict input validation to reject or properly escape format string specifiers in all user-supplied API parameters. Apply vendor-provided security patches for the XCC web interface. Consider implementing WAF rules to detect and block format string injection attempts as an interim measure.

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:< 2.93_afbt30p
Thinkagile Hx7530 FirmwareOperating system
Affected:< 2.93_afbt30p
Thinkagile Vx3331 FirmwareOperating system
Affected:< 2.93_afbt30p
Thinkagile Hx Enclosure FirmwareOperating system
Affected:< 3.72_tei388s
Thinkagile Hx1021 FirmwareOperating system
Affected:< 3.72_tei388s
Thinkagile Hx1320 FirmwareOperating system
Affected:< 8.88_cdi3a4a
Thinkagile Hx1321 FirmwareOperating system
Affected:< 8.88_cdi3a4a
Thinkagile Hx1331 FirmwareOperating system
Affected:< 2.93_afbt30p

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 device model and firmware version
    Access the Thinkagile device's BMC or XCC web interface. Navigate to the firmware or system information page to retrieve the current firmware version. Alternatively, use IPMI command: `ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> raw` or check via Lenovo XCC web portal under 'System Information' or 'Firmware Update' section.
    Affected if The displayed firmware version falls within the affected ranges (Hx5530/Hx7530/Vx3331/Hx1331 < 2.93_afbt30p, Hx Enclosure/Hx1021 < 3.72_tei388s, Hx1320/Hx1321 < 8.88_cdi3a4a)
  2. Confirm XCC web interface is enabled
    Verify that the XCC (ThinkAgile Center Controller) web interface is accessible by attempting to reach https://<bmc_ip> or https://<bmc_ip>/xcc in a browser. Check the BMC network settings to confirm XCC service is running.
    Affected if The XCC web interface responds and is reachable on the network, indicating the vulnerable component is active
  3. Check API access status
    Log into the XCC web interface and navigate to the API documentation or API endpoint section. Verify that API endpoints are accessible. Typically XCC exposes REST APIs at /api endpoints.
    Affected if API endpoints are accessible and respond to authenticated requests, meaning the attack surface exists
  4. Review API input handling (if accessible)
    If you have access to API testing tools, send a test authenticated request to any API parameter with a format string specifier such as %s, %x, or %n as part of the input value. Observe whether the application crashes, returns an error, or processes the input as a format string.
    Affected if The API accepts and processes format string specifiers without proper sanitization, causing unexpected behavior or errors

A Thinkagile device is affected if its firmware version is below the specified thresholds and the XCC web interface API is accessible to authenticated 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
Upgrade available Upgrade to 2.93_afbt30p / 3.72_tei388s / 8.88_cdi3a4a or later
Fixed in 2.93_afbt30p3.72_tei388s8.88_cdi3a4a
Interim mitigation

Implement strict input validation to reject or properly escape format string specifiers in all user-supplied API parameters. Apply vendor-provided security patches for the XCC web interface. Consider implementing WAF rules to detect and block format string injection attempts as an interim measure.

Recommended fix High confidence

Firmware >= 2.93_afbt30p (Hx5530/Hx7530/Vx3331/Hx1331), >= 3.72_tei388s (Hx Enclosure/Hx1021), >= 8.88_cdi3a4a (Hx1320/Hx1321)

  1. Identify the specific Thinkagile model from the affected list (Hx5530, Hx7530, Vx3331, Hx Enclosure, Hx1021, Hx1320, Hx1321, Hx1331)
  2. Navigate to Lenovo support portal at support.lenovo.com
  3. Locate the firmware download page for the specific Thinkagile model
  4. Download the firmware version 2.93_afbt30p or higher for Hx5530, Hx7530, Vx3331, Hx1331
  5. Download the firmware version 3.72_tei388s or higher for Hx Enclosure, Hx1021
  6. Download the firmware version 8.88_cdi3a4a or higher for Hx1320, Hx1321
  7. Follow Lenovo's standard firmware update procedure for the specific model (typically via XCC web interface or CLI)
  8. Verify the firmware version has been updated successfully after the update process completes
Caveat Firmware updates may require downtime; ensure proper backup and maintenance window planning before applying

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

Fix this in Thinkagile Hx5530 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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