CVE-2023-29056
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 LDAP user, under specific conditions, will default to read-only permissions when authenticating into XCC. To be vulnerable, XCC must be configured to use an LDAP server for Authentication/Authorization and have the login permission attribute not defined.
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 confidenceThis is an authentication/authorization misconfiguration in XCC where LDAP-authenticated users incorrectly default to read-only permissions when the login permission attribute is not defined in the LDAP configuration. An attacker with valid LDAP credentials can exploit this by authenticating to XCC and gaining unintended read-only access instead of proper authorized permissions.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 XCC firmware versionAccess the Lenovo XClarity Controller (XCC) web interface or use IPMI command 'ipmitool mc info' or check via Lenovo XCC REST API at /api/mc/info to retrieve the firmware version stringAffected if The installed firmware version is lower than the affected ranges (Thinkagile Hx5530/Hx7530/Vx3331: < 2.93_afbt30p, Hx Enclosure/Hx1021: < 3.72_tei388s, Hx1320/Hx1321: < 8.88_cdi3a4a, Hx1331: < 2.93_afbt30p)
-
Confirm LDAP authentication is enabledIn XCC web interface, navigate to Security > Authentication > LDAP Settings, or query via XCC API at /api/session/ldap to check if LDAP authentication is configured and activeAffected if LDAP authentication is enabled in XCC settings
-
Verify login permission attribute configurationIn XCC LDAP settings, examine the 'Login Permission' or 'User Permission Attribute' field. This is typically found under Security > Authentication > LDAP > LDAP Server Configuration. Check if a permission attribute is explicitly mapped (such as attribute mapping to XCC roles)Affected if The login permission attribute field is empty, not defined, or no attribute mapping is configured for LDAP user roles
You are affected if your Thinkagile device runs a vulnerable XCC firmware version AND has LDAP authentication enabled BUT lacks a defined login permission attribute mapping in the LDAP configuration, allowing LDAP users to default to read-only access.
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
Define the login permission attribute in the XCC LDAP configuration to ensure proper authorization levels are assigned during authentication.
Firmware 2.93_afbt30p (Hx5530/Hx7530/Vx3331/Hx1331), 3.72_tei388s (Hx Enclosure/Hx1021), or 8.88_cdi3a4a (Hx1320/Hx1321)
- 1. Identify the exact Thinkagile model from the affected list (Hx5530, Hx7530, Vx3331, Hx Enclosure, Hx1021, Hx1320, Hx1321, or Hx1331)
- 2. Access the Lenovo Support site (support.lenovo.com) and search for the specific model firmware
- 3. Download the firmware version 2.93_afbt30p or later for Hx5530/Hx7530/Vx3331/Hx1331 models
- 4. Download the firmware version 3.72_tei388s or later for Hx Enclosure/Hx1021 models
- 5. Download the firmware version 8.88_cdi3a4a or later for Hx1320/Hx1321 models
- 6. Apply the firmware update via XCC (XClarity Controller) web interface or using Lenovo XClarity Administrator
- 7. After update, verify XCC firmware version matches the fixed release
- 8. For additional hardening, ensure LDAP login permission attributes are properly defined in LDAP server configuration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing3.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 $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29056 — 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-29056 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