| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in SCALANCE M875 and classified as problematic. This impacts an unknown function. Performing a manipulation results in credentials management (Password). This vulnerability is reported as CVE-2018-11449. The attack requires a local approach. No exploit exists.
Details
A vulnerability classified as problematic has been found in SCALANCE M875 (the affected version unknown). This affects an unknown part. The manipulation with an unknown input leads to a credentials management vulnerability (Password). CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality. The summary by CVE is:
A vulnerability has been identified in SCALANCE M875 (All versions). An attacker with access to the local file system might obtain passwords for administratrive users. Successful exploitation requires read access to files on the local file system. A successful attack could allow an attacker to obtain administrative passwords. At the time of advisory publication no public exploitation of this security vulnerability was known.
The bug was discovered 06/12/2018. The weakness was disclosed 06/26/2018 (Website). The advisory is shared at cert-portal.siemens.com. This vulnerability is uniquely identified as CVE-2018-11449 since 05/25/2018. An attack has to be approached locally. A authentication is necessary for 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 14 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-120011, VDB-120012, VDB-120013 and VDB-119995 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: PasswordClass: Credentials management / Password
CWE: CWE-255
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/25/2018 🔍06/12/2018 🔍
06/26/2018 🔍
06/26/2018 🔍
06/27/2018 🔍
03/29/2023 🔍
Sources
Advisory: ssa-977428Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-11449 (🔍)
GCVE (CVE): GCVE-0-2018-11449
GCVE (VulDB): GCVE-100-119997
See also: 🔍
Entry
Created: 06/27/2018 17:43Updated: 03/29/2023 08:42
Changes: 06/27/2018 17:43 (57), 02/22/2020 16:16 (2), 03/29/2023 08:42 (3)
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.