Extreme Networks ExtremeWireless WiNG up to 5.8.6.8/5.9.1.2 AES Key credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Extreme Networks ExtremeWireless WiNG up to 5.8.6.8/5.9.1.2. It has been classified as critical. Affected by this issue is some unknown functionality of the component AES Key. The manipulation leads to credentials management. This vulnerability is uniquely identified as CVE-2018-5797. The attack can only be initiated within the local network. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, has been found in Extreme Networks ExtremeWireless WiNG up to 5.8.6.8/5.9.1.2. This issue affects an unknown code block of the component AES Key. The manipulation with an unknown input leads to a credentials management vulnerability. Using CWE to declare the problem leads to CWE-255. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in Extreme Networks ExtremeWireless WiNG 5.x before 5.8.6.9 and 5.9.x before 5.9.1.3. There is an Smint_encrypt Hardcoded AES Key that can be used for packet decryption (obtaining cleartext credentials) by an attacker who has access to a wired port.
The bug was discovered 01/19/2018. The weakness was disclosed 02/05/2018 (Website). The advisory is shared at gtacknowledge.extremenetworks.com. The identification of this vulnerability is CVE-2018-5797 since 01/19/2018. The exploitation is known to be easy. Access to the local network is required for this attack. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 16 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 5.8.6.9 or 5.9.1.3 eliminates this vulnerability.
The entries VDB-112807, VDB-112808, VDB-112809 and VDB-112810 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Credentials managementCWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Networks ExtremeWireless WiNG 5.8.6.9/5.9.1.3
Timeline
01/19/2018 🔍01/19/2018 🔍
02/04/2018 🔍
02/05/2018 🔍
02/05/2018 🔍
01/01/2020 🔍
Sources
Advisory: gtacknowledge.extremenetworks.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-5797 (🔍)
GCVE (CVE): GCVE-0-2018-5797
GCVE (VulDB): GCVE-100-112817
See also: 🔍
Entry
Created: 02/05/2018 14:59Updated: 01/01/2020 15:40
Changes: 02/05/2018 14:59 (60), 01/01/2020 15:40 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.