dbcve.org
Xclarity AdministratorApplication · Lenovo

CVE-2023-34418

HIGH · 8.1 CVSS v3.1 Published 2023-06-26
Fix available
A fix is available. Upgrade to 4.0.0 or later.
See remediation →
87/100
Remediation priority · High
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 may be able to gain unauthorized access to events and other data stored in LXCA due to a SQL injection vulnerability in a specific web 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

Lenovo XClarity Administrator (LXCA) contains a SQL injection vulnerability in a specific web API endpoint. An authenticated user with valid credentials can exploit this to execute unauthorized SQL queries, potentially accessing sensitive events and other data stored in the LXCA database.

MitigationApply the vendor-supplied patch for CVE-2023-34418. If no patch is available, implement input validation and convert the vulnerable API queries to use parameterized statements/prepared statements.

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.0.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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Confirm Lenovo XClarity Administrator is installed
    Locate the LXCA installation directory or check for the LXCA web service running on the host. Common locations include /opt/lxca or C:\Program Files\Lenovo\XClarity Administrator, or check if port 443/8443 is listening with the LXCA web interface.
    Affected if LXCA is not installed on the system
  2. Identify the installed LXCA version
    Access the LXCA web UI and navigate to About/Licensing page, or check the version file in the installation directory (typically version.txt or similar), or query the API endpoint /api/about.
    Affected if The version is below 4.0.0 (e.g., 3.x.x)
  3. Verify the vulnerable web API endpoint is accessible
    Attempt to reach the LXCA API endpoint. The vulnerable endpoint is a web API endpoint that accepts user input for SQL queries. Check if the API is reachable at the default LXCA ports (usually 443 or 8443).
    Affected if The API endpoint is accessible from the network without being blocked by firewall or network segmentation
  4. Confirm user authentication is enabled for LXCA
    Check that LXCA user authentication is configured and required for API access. Verify that valid user credentials exist in the LXCA user database.
    Affected if Authentication is enabled and valid credentials can be obtained (since the vulnerability requires an authenticated user)

The environment is affected if Lenovo XClarity Administrator is installed with a version lower than 4.0.0 and the web API endpoint is network-accessible with authentication enabled.

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.0.0 or later
Fixed in 4.0.0
Interim mitigation

Apply the vendor-supplied patch for CVE-2023-34418. If no patch is available, implement input validation and convert the vulnerable API queries to use parameterized statements/prepared statements.

Recommended fix Moderate confidence

Xclarity Administrator 4.0.0

  1. 1. Back up the current Xclarity Administrator configuration and data.
  2. 2. Download Lenovo Xclarity Administrator version 4.0.0 or later from the official Lenovo support website (support.lenovo.com).
  3. 3. Review the Lenovo Xclarity Administrator upgrade documentation for version 4.0.0.
  4. 4. Perform the upgrade following the documented upgrade procedure.
  5. 5. After upgrade, verify the SQL injection vulnerability is remediated by confirming the specific web API endpoint no longer accepts malicious SQL input.
  6. 6. Validate that existing LXCA functionality and user access controls work correctly after the upgrade.

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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