Intel RAID Web Console 3 up to 4.185 on Windows improper authentication

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Intel RAID Web Console 3 up to 4.185 on Windows. The impacted element is an unknown function. Performing a manipulation results in improper authentication. This vulnerability is reported as CVE-2018-3696. The attack requires a local approach. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Intel RAID Web Console 3 up to 4.185 on Windows. This affects an unknown code. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Authentication bypass in the Intel RAID Web Console 3 for Windows before 4.186 may allow an unprivileged user to potentially gain administrative privileges via local access.
The bug was discovered 11/13/2018. The weakness was disclosed 11/14/2018 (Website). The advisory is shared at intel.com. This vulnerability is uniquely identified as CVE-2018-3696 since 12/28/2017. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $5k-$25k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 371324 (Intel RAID Web Console 3 Multiple Vulnerabilities).
Upgrading to version 4.186 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 106028†). The entry VDB-126840 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.9
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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
Class: Improper authenticationCWE: CWE-287
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: RAID Web Console 3 4.186
Timeline
12/28/2017 🔍11/13/2018 🔍
11/13/2018 🔍
11/14/2018 🔍
11/14/2018 🔍
11/15/2018 🔍
04/12/2020 🔍
Sources
Vendor: intel.comAdvisory: intel.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-3696 (🔍)
GCVE (CVE): GCVE-0-2018-3696
GCVE (VulDB): GCVE-100-126837
SecurityFocus: 106028 - Intel RAID Web Console CVE-2018-3696 Authentication Bypass Vulnerability
See also: 🔍
Entry
Created: 11/15/2018 07:53Updated: 04/12/2020 21:08
Changes: 11/15/2018 07:53 (63), 04/12/2020 21:08 (4)
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.