What is CVE-2019-6156?A low-severity flaw in 510-15ikl Firmware, explained.
CVE-2019-6156 is a low-severity flaw (CVSS 3.3) in 510-15ikl Firmware from Lenovo, published on 10 April 2019. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.2%. If you run an affected version, plan in the vendor’s fix.
Published 10 April 2019. Record last updated 24 August 2020. We keep this page's data up to date.
What is CVE-2019-6156? In plain terms.
An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can change some data.
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.
What kind of flaw is it?
- CWE-667Improper Locking
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan change some data
Severity vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Is CVE-2019-6156 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.2%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2019-6156 scores 12. Action: Track.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2019-6156 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2019-6156? 354 products.
The published record lists 354 products from 1 vendor. Versions are shown as published: "before r0met46w" means every version up to, but not including, r0met46w. If you run one of these, check your version, then go to the fix below.
- Operating system
510-15ikl Firmware
by Lenovo
Affected versionsversion not specified - Operating system
Thinkpad S5 Firmware
by Lenovo
Affected versionsbefore r0met46wbefore r09et70w - Hardware
330-14igm
by Lenovo
Affected versionsversion not specified - Operating system
330-14igm Firmware
by Lenovo
Affected versionsbefore 7xcn30ww - Hardware
330-15igm
by Lenovo
Affected versionsversion not specified - Operating system
330-15igm Firmware
by Lenovo
Affected versionsbefore 7xcn30ww - Hardware
510-15ikl
by Lenovo
Affected versionsversion not specified - Hardware
510s-08ikl
by Lenovo
Affected versionsversion not specified - Operating system
510s-08ikl Firmware
by Lenovo
Affected versionsversion not specified
How do I fix CVE-2019-6156? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
1 linkDoes CVE-2019-6156 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
In Lenovo systems, SMM BIOS Write Protection is used to prevent writes to SPI Flash. While this provides sufficient protection, an additional layer of protec...
- Matched to
- 510-15ikl Firmware on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2019-6156 is a low-severity flaw in 510-15ikl Firmware from Lenovo, published on 10 April 2019. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can change some data.
It scores 3.3 out of 10 on the CVSS severity scale, which is low. Our risk score for CVE-2019-6156 is 12 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.2%. That can change at any time, which is why we keep watching.
For 510-15ikl Firmware from Lenovo: version not specified. The record lists 354 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.