CVE-2021-3519: A vulnerability was reported in some Lenovo Desktop models that could allow unauthorized access to the boot menu, when the "BIOS Password At
Noroxi assessment
Priority: Monitor (action score 27/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.23% (FIRST EPSS).
- Physical access to the device is required. No account or password is 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
A vulnerability was reported in some Lenovo Desktop models that could allow unauthorized access to the boot menu, when the "BIOS Password At Boot Device List" BIOS setting is Yes.
- Published
- Nov 12, 2021
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-287
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 6.8
- CNA · lenovo
- 6.4
- 0.4 point gap
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
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 | ideacentre c5-14mb05 firmware | cpe:2.3:o:lenovo:ideacentre_c5-14mb05_firmware |
| lenovo | ideacentre c5-14mb05 | cpe:2.3:h:lenovo:ideacentre_c5-14mb05 |
| lenovo | ideacentre 3-07imb05 firmware | cpe:2.3:o:lenovo:ideacentre_3-07imb05_firmware |
| lenovo | ideacentre 3-07imb05 | cpe:2.3:h:lenovo:ideacentre_3-07imb05 |
| lenovo | ideacentre 5-14imb05 firmware | cpe:2.3:o:lenovo:ideacentre_5-14imb05_firmware |
| lenovo | ideacentre 5-14imb05 | cpe:2.3:h:lenovo:ideacentre_5-14imb05 |
| lenovo | ideacentre 5-14iob6 firmware | cpe:2.3:o:lenovo:ideacentre_5-14iob6_firmware |
| lenovo | ideacentre 5-14iob6 | cpe:2.3:h:lenovo:ideacentre_5-14iob6 |
| lenovo | ideacentre creator 5-14iob6 firmware | cpe:2.3:o:lenovo:ideacentre_creator_5-14iob6_firmware |
| lenovo | ideacentre creator 5-14iob6 | cpe:2.3:h:lenovo:ideacentre_creator_5-14iob6 |
| lenovo | ideacentre g5-14imb05 firmware | cpe:2.3:o:lenovo:ideacentre_g5-14imb05_firmware |
| lenovo | ideacentre g5-14imb05 | cpe:2.3:h:lenovo:ideacentre_g5-14imb05 |
and 107 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lenovo ideacentre 3-07imb05 firmwarebefore m2vkt18a
- lenovo ideacentre 310s-08igm firmwareup to m1tkt31a inclusive
- lenovo ideacentre 5-14imb05 firmwarebefore o4hkt33a
- lenovo ideacentre 5-14iob6 firmwarebefore m3gkt29a
- lenovo ideacentre 510a-15arr firmwareup to o4dkt41a inclusive
- lenovo ideacentre 510s-07icb firmwarebefore m22kt46a
- lenovo ideacentre 510s-07ick firmwarebefore m30kt24a
- lenovo ideacentre 510s-07ick firmwarebefore m30kt23a
- lenovo ideacentre c5-14mb05 firmwarebefore o4hkt33a
- lenovo ideacentre creator 5-14iob6 firmwarebefore m3gkt29a
- lenovo ideacentre g5-14imb05 firmwarebefore o4hkt33a
- lenovo ideacentre gaming 5-14iob6 firmwarebefore m3gkt29a
- lenovo thinkcentre e75 t/s firmwarebefore m16kt67a
- lenovo thinkcentre m60e tiny firmwarebefore m3skt1ea
- lenovo thinkcentre m630e firmwarebefore m28kt36a
- lenovo thinkcentre m70a firmwareup to m2skt21a inclusive
- lenovo thinkcentre m70a gen 2 firmwarebefore m3nkt17a
- lenovo thinkcentre m70c firmwarebefore m2vkt18a
- lenovo thinkcentre m70q firmwarebefore m2wkt49a
- lenovo thinkcentre m70s firmwarebefore m2tkt3ca
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 Desktop BIOS
- variousaffected
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.
No history yet (it accumulates with the daily EPSS job).
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.
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
- Physical access to the device is required.
- No account or password is 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
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);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)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
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.