CVE-2024-8280· NVD / CVE Program· CNA lenovo

An input validation weakness was discovered in XCC that could allow a valid, authenticated XCC user with elevated privileges to perform comm

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 63.4% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An input validation weakness was discovered in XCC that could allow a valid, authenticated XCC user with elevated privileges to perform command injection or cause a recoverable denial of service using a specially crafted file.

HighCVSS 7.2 · v3.1—No exploit No fix recorded

Published: Sep 13, 2024
Updated: Jun 17, 2026
EPSS: 1.0% · 63th percentile
CWE: CWE-78

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.0%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · lenovo: 7.2; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

ProductVersion

Vendor	Product	CPE
lenovo	thinkagile vx7531 firmware	cpe:2.3:o:lenovo:thinkagile_vx7531_firmware
lenovo	thinkagile vx7530 firmware	cpe:2.3:o:lenovo:thinkagile_vx7530_firmware
lenovo	thinkagile vx7330 firmware	cpe:2.3:o:lenovo:thinkagile_vx7330_firmware
lenovo	thinkagile vx5530 firmware	cpe:2.3:o:lenovo:thinkagile_vx5530_firmware
lenovo	thinkagile vx3530-g firmware	cpe:2.3:o:lenovo:thinkagile_vx3530-g_firmware
lenovo	thinkagile vx3330 firmware	cpe:2.3:o:lenovo:thinkagile_vx3330_firmware
lenovo	thinkagile vx2330 firmware	cpe:2.3:o:lenovo:thinkagile_vx2330_firmware
lenovo	thinksystem sr650 v2 firmware	cpe:2.3:o:lenovo:thinksystem_sr650_v2_firmware
lenovo	thinksystem sr630 v2 firmware	cpe:2.3:o:lenovo:thinksystem_sr630_v2_firmware
lenovo	thinkagile mx3531-f all-flash firmware	cpe:2.3:o:lenovo:thinkagile_mx3531-f_all-flash_firmware
lenovo	thinkagile mx3531 h hybrid firmware	cpe:2.3:o:lenovo:thinkagile_mx3531_h_hybrid_firmware
lenovo	thinkagile mx3530 f all flash firmware	cpe:2.3:o:lenovo:thinkagile_mx3530_f_all_flash_firmware

and 38 more

Versions reported by the vendor

Affected version ranges reported by the assigning authority (lenovo). Independent of NVD's CPE analysis and usually ahead of it.

Lenovo HX Enclosure Certified Node (ThinkAgile) XCC
- before 6.36 TEI3F4Aaffected
Lenovo HX1021 Edge Certified Node 3yr (ThinkAgile) XCC
- before 4.11 TEI3E4Aaffected
Lenovo HX1320 Appliance (ThinkAgile) XCC
- before 9.97 CDI3B4Baffected
Lenovo HX1321 Certified Node (ThinkAgile) XCC
- before 9.97 CDI3B4Baffected
Lenovo HX1331 Certified Node (ThinkAgile) XCC
- before 4.71 AFBT48Caffected
Lenovo HX1520-R Appliance (ThinkAgile) XCC
- before 9.97 CDI3B4Baffected
Lenovo HX1521-R Certified Node (ThinkAgile) XCC
- before 9.97 CDI3B4Baffected
Lenovo HX2320-E Appliance (ThinkAgile) XCC
- before 9.97 CDI3B4Baffected
Lenovo HX2321 Certified Node (ThinkAgile) XCC
- before 9.97 CDI3B4Baffected
Lenovo HX2330 Appliance (ThinkAgile) XCC
- before 4.71 AFBT48Caffected
Lenovo HX2331 Certified Node (ThinkAgile) XCC
- before 4.71 AFBT48Caffected
Lenovo HX2720-E Appliance (ThinkAgile) XCC
- before 6.36 TEI3F4Aaffected

Same product

lenovo: all records

Other highest-scoring records for the same primary product.

CVE-2024-8281An input validation weakness was discovered in XCC that could allow a valid, authenticated XCC user with elevated privileges to perform comm
28Monitor
CVE-2024-8279A privilege escalation vulnerability was discovered in XCC that could allow a valid, authenticated XCC user with elevated privileges to perf
28Monitor
CVE-2024-8278A privilege escalation vulnerability was discovered in XCC that could allow a valid, authenticated XCC user with elevated privileges to perf
28Monitor

Published before and after this one in the same product

← EarlierCVE-2024-8059Sep 13, 2024 · IPMI credentials may be captured in XCC audit log entries when the account username length is 16 characters.
17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-82780 days apartA privilege escalation vulnerability was discovered in XCC that could allow a valid, authenticated XCC user with elevated privileges to perf
28Monitor
CVE-2024-82790 days apartA privilege escalation vulnerability was discovered in XCC that could allow a valid, authenticated XCC user with elevated privileges to perf
28Monitor
CVE-2024-82810 days apartAn input validation weakness was discovered in XCC that could allow a valid, authenticated XCC user with elevated privileges to perform comm
28Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

The bug in code

The whole CWE-78 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const host = req.body.host;
2exec("ping -c 1 " + host, onResult);

Fixed

1const host = req.body.host;
2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

support.lenovo.com/us/en/product_security/LEN-172051

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records