makepasswd 1.10 insecure default initialization of resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in makepasswd 1.10 and classified as problematic. The affected element is an unknown function. The manipulation leads to insecure default initialization of resource. This vulnerability is referenced as CVE-2010-2247. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in makepasswd 1.10 and classified as problematic. This issue affects an unknown part. The manipulation with an unknown input leads to a insecure default initialization of resource vulnerability. Using CWE to declare the problem leads to CWE-1188. The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure. Impacted is confidentiality. The summary by CVE is:
makepasswd 1.10 default settings generate insecure passwords
The weakness was published 11/06/2019. The identification of this vulnerability is CVE-2010-2247 since 06/09/2010. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
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: Insecure default initialization of resourceCWE: CWE-1188
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
06/09/2010 🔍11/06/2019 🔍
11/07/2019 🔍
02/05/2024 🔍
Sources
Advisory: FEDORA-2020-1db19e75dbStatus: Not defined
CVE: CVE-2010-2247 (🔍)
GCVE (CVE): GCVE-0-2010-2247
GCVE (VulDB): GCVE-100-145085
Entry
Created: 11/07/2019 08:13Updated: 02/05/2024 08:38
Changes: 11/07/2019 08:13 (34), 11/07/2019 08:18 (17), 02/05/2024 08:38 (4)
Complete: 🔍
Cache ID: 216:F93: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.