CVE-2023-4608
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 · uneditedAn authenticated XCC user with elevated privileges can perform blind SQL injection in limited cases through a crafted API command. This affects ThinkSystem v2 and v3 servers with XCC; ThinkSystem v1 servers are not affected.
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 confidenceLenovo ThinkSystem v2 and v3 servers running XCC (XClarity Controller) firmware contain an authenticated blind SQL injection vulnerability. An attacker with elevated privileges can inject malicious SQL queries through crafted API commands, potentially allowing unauthorized data access or database manipulation.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the ThinkAgile modelAccess the server's BMC or XCC web interface and check the system model name under Hardware Inventory or System Information. Alternatively, run command: dmidecode -s system-product-name or check the physical server label.Affected if The model is one of: Thinkagile Hx5530, Hx7530, Vx3331, Hx1331, Hx2330, Hx2331, Hx3330, or Hx3331
-
Confirm XCC firmware versionLog into the XClarity Controller (XCC) web UI or CLI. In the web interface, go to BMC Settings or Firmware Updates. From CLI, run: ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> mc info or access XCC REST API endpoint /api/mc/info.Affected if XCC firmware is present and running (any version on affected models) since all versions are vulnerable
-
Verify XCC management interface is network accessibleCheck if port 443 (HTTPS) or 80 (HTTP) on the BMC/XCC IP is reachable from your network. Use: nmap -p 443 <bmc_ip> or telnet <bmc_ip> 443.Affected if The XCC web interface is exposed on the network, allowing API command injection vectors
-
Audit XCC user accounts with elevated privilegesLog into XCC and navigate to User Accounts or use ipmitool: ipmitool -I lanplus -H <bmc_ip> -U <user> -P <pass> user list to list all users and privilege levels. Check for accounts with Administrator or Operator privileges.Affected if There are one or more user accounts configured with Administrator or elevated privileges, which are required for the authenticated SQL injection to be exploitable
If the server is any of the listed ThinkAgile models with XCC firmware accessible on the network and has administrative accounts configured, the environment is affected by this vulnerability.
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.
From vendor dataApply Lenovo-provided XCC firmware patches when released; restrict administrative XCC access to trusted personnel only and isolate management networks.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4608 — 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-4608 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