Intel Driver/Support Assistant up to 3.1.0 SEMA Driver Memory input validation

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Intel Driver and Support Assistant up to 3.1.0. This affects an unknown function of the component SEMA Driver. The manipulation leads to input validation (Memory). This vulnerability is documented as CVE-2018-3610. The attack needs to be performed locally. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Intel Driver and Support Assistant up to 3.1.0 (Hardware Driver Software). It has been rated as critical. This issue affects an unknown functionality of the component SEMA Driver. The manipulation with an unknown input leads to a input validation vulnerability (Memory). Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
SEMA driver in Intel Driver and Support Assistant before version 3.1.1 allows a local attacker the ability to read and writing to Memory Status registers potentially allowing information disclosure or a denial of service condition.
The bug was discovered 01/09/2018. The weakness was released 01/09/2018 (Website). The advisory is shared at security-center.intel.com. The identification of this vulnerability is CVE-2018-3610 since 12/28/2017. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 370726 (Intel Driver and Support Assistant Information Disclosure Vulnerability. (INTEL-SA-00108)).
Upgrading to version 3.1.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.intel.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.0
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: MemoryClass: Input validation / Memory
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Driver/Support Assistant 3.1.1
Timeline
12/28/2017 🔍01/09/2018 🔍
01/09/2018 🔍
01/09/2018 🔍
01/10/2018 🔍
12/21/2019 🔍
Sources
Vendor: intel.comAdvisory: security-center.intel.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-3610 (🔍)
GCVE (CVE): GCVE-0-2018-3610
GCVE (VulDB): GCVE-100-111581
Entry
Created: 01/10/2018 14:21Updated: 12/21/2019 07:16
Changes: 01/10/2018 14:21 (62), 12/21/2019 07:16 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.