dbcve.org
Thinkagile Hx5530 FirmwareOperating system · Lenovo

CVE-2023-0683

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 XCC user with read only access may gain elevated privileges through a specifically crafted API call.

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

A privilege escalation vulnerability exists where an authenticated user with read-only access to XCC can gain elevated privileges through a specifically crafted API call, bypassing intended authorization controls.

MitigationApply vendor-supplied patches or updates for XCC. Review and restrict API permissions for read-only accounts until the patch is deployed.

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 the Thinkagile model
    Access the Lenovo XClarity Controller (XCC) web interface or use IPMI/Redfish to query the system hardware information. Look for the specific model name such as Hx5530, Hx7530, Vx3331, Hx1021, Hx1320, Hx1321, Hx1331, or the enclosure type.
    Affected if The model is one of the affected Thinkagile products listed in the CVE (Hx5530, Hx7530, Vx3331, Hx Enclosure, Hx1021, Hx1320, Hx1321, or Hx1331).
  2. Check the XCC firmware version
    In the XCC web interface, navigate to the Firmware Update or BMC Settings section to view the current firmware version. Alternatively, use IPMI command: 'ipmitool -I lanplus -H <XCC_IP> -U <user> -P <pass> raw' or Redfish GET request to /api/settings to retrieve the firmware version string.
    Affected if The installed firmware version is lower than the threshold for your model (Hx5530/Hx7530/Vx3331/Hx1331: < 2.93_afbt30p, Hx Enclosure/Hx1021: < 3.72_tei388s, Hx1320/Hx1321: < 8.88_cdi3a4a).
  3. Verify XCC authentication is enabled
    Confirm that XCC user authentication is active by attempting to log in with valid credentials or checking the security settings in the XCC web interface under User Administration or Access Settings.
    Affected if XCC is accessible and accepts authentication, meaning the vulnerability can be exploited by an authenticated user.
  4. Identify read-only user accounts
    In the XCC interface, review the User Administration section to enumerate accounts and their permission levels. Look for accounts with read-only or restricted roles assigned.
    Affected if There exists at least one user account with read-only or limited privileges, as this is the prerequisite for exploiting the privilege escalation flaw.

You are affected if you are running a Thinkagile model listed in the CVE with an XCC firmware version below the specified threshold, and you have read-only user accounts configured in XCC.

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

Apply vendor-supplied patches or updates for XCC. Review and restrict API permissions for read-only accounts until the patch is deployed.

Recommended fix High confidence

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

  1. 1. Identify the specific ThinkAgile model in your environment from the affected products list
  2. 2. Navigate to Lenovo Support (support.lenovo.com) and locate the firmware download page for your specific model
  3. 3. Download the appropriate fixed firmware version: 2.93_afbt30p for Hx5530, Hx7530, Vx3331, Hx1331; 3.72_tei388s for Hx Enclosure, Hx1021; 8.88_cdi3a4a for Hx1320, Hx1321
  4. 4. Review the firmware update instructions provided by Lenovo for your specific hardware
  5. 5. Apply the firmware update following Lenovo's standard XCC firmware update procedure
  6. 6. After update, verify the XCC firmware version matches the fixed release
  7. 7. Confirm the vulnerability is remediated by testing that read-only users cannot escalate privileges via API calls
Caveat Firmware updates to XCC may require downtime and should be tested in a staging environment before production deployment

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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