Skip to content
Noroxi
NVD / CVE Program· CNA lenovo

CVE-2019-6156: In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash.

Noroxi assessment

Priority: Monitor (action score 13/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).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. 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

In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash. While this provides sufficient protection, an additional layer of protection is provided by SPI Protected Range Registers (PRx). Lenovo was notified that after resuming from S3 sleep mode in various versions of BIOS for Lenovo systems, the PRx is not set. This does not impact the SMM BIOS Write Protection, which keeps systems protected.

LowCVSS 3.3 · v3.0—No exploit No fix recorded
Published
Apr 10, 2019
Updated
Jun 16, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

13

Monitor

Low priority for now.

CVSS
13 / 40 · 3.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2019-6156

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for lenovo records

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.

VendorProduct
lenovo510-15ikl firmware
lenovo510-15ikl
lenovo510s-08ikl firmware
lenovo510s-08ikl
lenovoideacentre 300-20ish firmware
lenovoideacentre 300-20ish
lenovoideacentre 300s-11ish firmware
lenovoideacentre 300s-11ish
lenovoideacentre 510-15icb firmware
lenovoideacentre 510-15icb
lenovoideacentre 510a-15icb firmware
lenovoideacentre 510a-15icb

and 188 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • lenovo 330-14igm firmwarebefore 7xcn30ww
  • lenovo 330-15igm firmwarebefore 7xcn30ww
  • lenovo 510-15ikl firmwareall versions
  • lenovo 510s-08ikl firmwareall versions
  • lenovo 530s-07icb firmwareall versions
  • lenovo aio 910-27ish firmwarebefore o37kt13a
  • lenovo aio y910-27ish firmwareall versions
  • lenovo aio300-23isu(c5130) firmwarebefore o1lkt46a
  • lenovo aio520-22ikl firmwareall versions
  • lenovo aio520-22iku firmwareall versions
  • lenovo aio520-24ikl firmwareall versions
  • lenovo aio520-24iku firmwareall versions
  • lenovo aio520-27ikl firmwareall versions
  • lenovo h50-30g desktop firmwareall versions
  • lenovo ideacentre 300-20ish firmwareall versions
  • lenovo ideacentre 300s-11ish firmwareall versions
  • lenovo ideacentre 510-15icb firmwarebefore o3qkt32a
  • lenovo ideacentre 510a-15icb firmwarebefore o3qkt32a
  • lenovo ideacentre 510s-08ish firmwareall versions
  • lenovo ideacentre 520s-23iku firmwarebefore o34kt23a

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 BIOS

    • variousaffected

Same product

lenovo: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-6188ThinkPad T460p and T470p BIOS Tamper Mechanism
    39Monitor
  • CVE-2019-6172A potential vulnerability in the SMI callback function used in Legacy USB driver using passed parameter without sufficient checking in some
    25Monitor
  • CVE-2019-6170A potential vulnerability in the SMI callback function used in the Legacy USB driver using boot services structure in runtime phase in some
    25Monitor

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.

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

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

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

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.

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.

All records