CVE-2023-29058
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 · uneditedA valid, authenticated XCC user with read-only permissions can modify custom user roles on other user accounts and the user trespass message through the XCC CLI. There is no exposure if SSH is disabled or if there are no users assigned optional read-only permissions.
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 confidenceA privilege escalation vulnerability in the XCC CLI allows authenticated users with read-only permissions to modify custom user roles on other accounts and the user trespass message, bypassing intended read-only access controls. The vulnerability stems from insufficient authorization checks in the CLI when handling role modifications.
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< 2.93_afbt30p< 2.93_afbt30p< 2.93_afbt30p< 3.72_tei388s< 3.72_tei388s< 8.88_cdi3a4a< 8.88_cdi3a4a< 2.93_afbt30pCVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Thinkagile model and XCC firmware versionAccess the XCC (XClarity Controller) web interface or use Lenovo OneCLI/LSISTA command 'onecli ic enable' to retrieve the BMC firmware version. For IPMI, use 'ipmitool -I lanplus -H <XCC_IP> -U <user> -P <pass> raw command' to query firmware info.Affected if The device is a Thinkagile Hx5530, Hx7530, Vx3331, Hx Enclosure, Hx1021, Hx1320, Hx1321, or Hx1331 and the firmware version is below 2.93_afbt30p (for Hx5530, Hx7530, Vx3331, Hx1331), 3.72_tei388s (for Hx Enclosure, Hx1021), or 8.88_cdi3a4a (for Hx1320, Hx1321)
-
Confirm XCC CLI is accessibleAttempt to access the XCC CLI via SSH to the BMC IP address using valid credentials: 'ssh <user>@<XCC_IP>' or use the XCC serial console. Verify the CLI interface is reachable and functional.Affected if XCC CLI is enabled and accessible on the affected Thinkagile device
-
Check for users with read-only permissionsWithin the XCC CLI, navigate to User Management or use the 'user' command to list all defined users and their assigned roles. Look for accounts that have 'ReadOnly', 'Viewer', or limited permissions rather than Administrator or full control roles.Affected if There exist user accounts with read-only or limited permissions on the system
-
Verify presence of custom user rolesIn XCC CLI, examine the role definitions using 'role' or 'user role' commands. Look for any custom-defined roles that may have been created beyond the default built-in roles.Affected if Custom user roles are defined in the XCC configuration
A user is affected if they operate a listed Thinkagile model with firmware below the specified version thresholds AND have XCC CLI accessible with read-only users present in the environment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.93_afbt30p3.72_tei388s8.88_cdi3a4a
If SSH is not required, disable it; otherwise ensure no users are assigned optional read-only permissions until a patch is applied to enforce proper authorization checks in the XCC CLI.
Firmware 2.93_afbt30p (Hx5530/Hx7530/Vx3331/Hx1331), 3.72_tei388s (Hx Enclosure/Hx1021), or 8.88_cdi3a4a (Hx1320/Hx1321)
- 1. Identify the Thinkagile model in use and note the current firmware version via XCC CLI or web interface
- 2. Navigate to Lenovo Support (support.lenovo.com) and search for the specific Thinkagile model firmware
- 3. Download the fixed firmware version: 2.93_afbt30p or later for Hx5530, Hx7530, Vx3331, Hx1331; 3.72_tei388s or later for Hx Enclosure, Hx1021; 8.88_cdi3a4a or later for Hx1320, Hx1321
- 4. Upload the firmware through XCC web interface (XCC Settings > Firmware Update) or CLI using the update command
- 5. Reboot the server as prompted to apply the firmware update
- 6. Verify the firmware version has been updated successfully
- 7. As a secondary mitigation, if SSH access is not required, disable SSH in XCC to eliminate any exposure vector
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29058 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-29058 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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