An unauthenticated denial of service vulnerability exists in the SMM v1, SMM v2, and FPC management web server which can be triggered under
Noroxi assessment
Priority: Monitor (action score 30/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: 0.61% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- 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 unauthenticated denial of service vulnerability exists in the SMM v1, SMM v2, and FPC management web server which can be triggered under crafted conditions. Rebooting SMM or FPC will restore access to the management web server.
- Published
- Jun 26, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 48th percentile
- CWE
- CWE-405
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · lenovo
- 7.5
- agree
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
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| lenovo | nextscale n1200 enclosure firmware | cpe:2.3:o:lenovo:nextscale_n1200_enclosure_firmware |
| lenovo | nextscale n1200 enclosure | cpe:2.3:h:lenovo:nextscale_n1200_enclosure |
| lenovo | thinkagile cp-cb-10 firmware | cpe:2.3:o:lenovo:thinkagile_cp-cb-10_firmware |
| lenovo | thinkagile cp-cb-10 | cpe:2.3:h:lenovo:thinkagile_cp-cb-10 |
| lenovo | thinkagile cp-cb-10e firmware | cpe:2.3:o:lenovo:thinkagile_cp-cb-10e_firmware |
| lenovo | thinkagile cp-cb-10e | cpe:2.3:h:lenovo:thinkagile_cp-cb-10e |
| lenovo | thinkagile hx enclosure certified node firmware | cpe:2.3:o:lenovo:thinkagile_hx_enclosure_certified_node_firmware |
| lenovo | thinkagile hx enclosure certified node | cpe:2.3:h:lenovo:thinkagile_hx_enclosure_certified_node |
| lenovo | thinkagile vx enclosure firmware | cpe:2.3:o:lenovo:thinkagile_vx_enclosure_firmware |
| lenovo | thinkagile vx enclosure | cpe:2.3:h:lenovo:thinkagile_vx_enclosure |
| lenovo | thinksystem d2 enclosure firmware | cpe:2.3:o:lenovo:thinksystem_d2_enclosure_firmware |
| lenovo | thinksystem d2 enclosure | cpe:2.3:h:lenovo:thinksystem_d2_enclosure |
and 4 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo nextscale n1200 enclosure firmwarebefore fhet60b-3.40
- lenovo thinkagile cp-cb-10 firmwarebefore tesm38c-1.26
- lenovo thinkagile cp-cb-10e firmwarebefore tesm38c-1.26
- lenovo thinkagile hx enclosure certified node firmwarebefore tesm38c-1.26
- lenovo thinkagile vx enclosure firmwarebefore tesm38c-1.26
- lenovo thinksystem d2 enclosure firmwarebefore tesm38c-1.26
- lenovo thinksystem da240 enclosure firmwarebefore umsm10s-1.07
- lenovo thinksystem dw612 enclosure firmwarebefore umsm10s-1.07
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 Fan Power Controller (FPC)
- variousaffected
Lenovo System Management Module (SMM)
- variousaffected
Same product
lenovo: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3897An authentication bypass vulnerability was discovered in an internal service of the Lenovo Fan Power Controller2 (FPC2) and Lenovo System Ma39Monitor
- CVE-2021-3849An authentication bypass vulnerability was discovered in the web interface of the Lenovo Fan Power Controller2 (FPC2) and Lenovo System Mana39Monitor
- CVE-2024-2659
A command injection vulnerability was identified in SMM/SMM2 and FPC that could allow an authenticated user with elevated privileges to exe28Monitor
Published before and after this one in the same product
- Later →CVE-2023-2993Jun 26, 2023 · A valid, authenticated user with limited privileges may be able to use specifically crafted web management server API calls to execute a lim25Monitor
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.
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 researchersFinders, 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.
No nightly-computed relations.
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.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-405 · Asymmetric Resource Consumption (Amplification)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.