Iomega/Lenovo/LenovoEMC NAS up to 4.1.402.34662 Password Change Session Token session fixiation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Iomega/Lenovo/LenovoEMC NAS up to 4.1.402.34662. It has been classified as critical. This affects an unknown function of the component Password Change Handler. Performing a manipulation results in session fixiation (Session Token). This vulnerability is known as CVE-2018-9082. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical has been found in Iomega/Lenovo/LenovoEMC NAS up to 4.1.402.34662. This affects an unknown code block of the component Password Change Handler. The manipulation with an unknown input leads to a session fixiation vulnerability (Session Token). CWE is classifying the issue as CWE-384. Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
For some Iomega, Lenovo, LenovoEMC NAS devices versions 4.1.402.34662 and earlier, the password changing functionality available to authenticated users does not require the user's current password to set a new one. As a result, attackers with access to the user's session tokens can change their password and retain access to the user's account
The bug was discovered 09/28/2018. The weakness was published 09/28/2018 (Website). The advisory is shared at support.lenovo.com. This vulnerability is uniquely identified as CVE-2018-9082 since 03/27/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-124597, VDB-124598, VDB-124599 and VDB-124600. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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: Session TokenClass: Session fixiation / Session Token
CWE: CWE-384
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/27/2018 🔍09/28/2018 🔍
09/28/2018 🔍
09/28/2018 🔍
09/29/2018 🔍
03/28/2020 🔍
Sources
Advisory: support.lenovo.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-9082 (🔍)
GCVE (CVE): GCVE-0-2018-9082
GCVE (VulDB): GCVE-100-124605
See also: 🔍
Entry
Created: 09/29/2018 12:30Updated: 03/28/2020 09:49
Changes: 09/29/2018 12:30 (58), 03/28/2020 09:49 (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.