dbcve.org
Xclarity AdministratorApplication · Lenovo

CVE-2024-45104

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-13
Fix available
A fix is available. Upgrade to 4.1.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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 LXCA user without sufficient privileges may be able to use the device identifier to modify an LXCA managed device through a specially crafted web 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

This is an insecure direct object reference (IDOR) or broken access control vulnerability in Lenovo XClarity Administrator (LXCA). An authenticated user with insufficient privileges can manipulate a device identifier in a crafted web API call to modify managed devices they should not have access to modify.

MitigationApply the vendor-supplied patch for LXCA. Until patched, monitor API access logs for unauthorized device modifications and restrict API permissions for low-privilege 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
Xclarity AdministratorApplication
Affected:< 4.1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed LXCA version
    Access the LXCA admin interface and navigate to About or Settings to view the version number, or run 'lxcactl --version' from the LXCA server command line if available
    Affected if The version displayed is lower than 4.1.0 (e.g., 4.0.x, 3.x, or earlier)
  2. Confirm web API accessibility
    Attempt to reach the LXCA API endpoint (typically https://<lxca-host>/api) using a web browser or curl command from an authenticated session
    Affected if The API endpoint responds and accepts requests, indicating the REST API is enabled
  3. Review API access logs for unauthorized device modifications
    Examine LXCA audit or access logs for POST/PUT requests to /api/devices or similar endpoints where the requesting user lacks administrative privileges over the target device
    Affected if Logs show device modification requests from low-privilege users targeting devices outside their assigned scope
  4. Inspect user role assignments
    In LXCA admin console, review User Management or Security settings to identify users with limited or custom roles who have API access
    Affected if Non-admin users exist who have API access permissions but are not granted full administrator rights to all managed devices

You are affected if LXCA version is below 4.1.0 and the web API is accessible to authenticated users with restricted device permissions.

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 4.1.0 or later
Fixed in 4.1.0
Interim mitigation

Apply the vendor-supplied patch for LXCA. Until patched, monitor API access logs for unauthorized device modifications and restrict API permissions for low-privilege users.

Recommended fix Moderate confidence

4.1.0

  1. 1. Back up the current Xclarity Administrator configuration and data.
  2. 2. Download Xclarity Administrator version 4.1.0 from Lenovo support (support.lenovo.com).
  3. 3. Review the upgrade guide and release notes for version 4.1.0 for any prerequisites.
  4. 4. Stop Xclarity Administrator services before upgrading.
  5. 5. Install version 4.1.0 following the standard upgrade procedure.
  6. 6. After upgrade, verify the Xclarity Administrator services start correctly.
  7. 7. Confirm the vulnerability is resolved by testing API access controls for unprivileged users.

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

Fix this in Xclarity Administrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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