CVE-2016-8231
First published: Sat Jun 03 2017(Updated: )
In Lenovo Service Bridge before version 4, a bug found in the signature verification logic of the code signing certificate could be exploited by an attacker to insert a forged code signing certificate.
Credit: psirt@lenovo.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Lenovo Lenovo Service Bridge |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-8231?
CVE-2016-8231 is rated as a medium severity vulnerability.
How do I fix CVE-2016-8231?
To fix CVE-2016-8231, upgrade to Lenovo Service Bridge version 4 or later.
What kind of attack does CVE-2016-8231 enable?
CVE-2016-8231 allows an attacker to exploit the vulnerability to insert a forged code signing certificate.
Which versions of Lenovo Service Bridge are affected by CVE-2016-8231?
Lenovo Service Bridge versions prior to 4 are affected by CVE-2016-8231.
Is there a workaround for CVE-2016-8231?
There are no official workarounds for CVE-2016-8231; updating is recommended.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/severity
- agent/last-modified-date
- agent/author
- agent/weakness
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- vendor/lenovo
- canonical/lenovo lenovo service bridge