CVE-2010-2247 json
makepasswd 1.10 default settings generate insecure passwords
published 2019-11-06 7 y ago modified 2026-06-16 4 mo ago also EUVD-2010-2259
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
makepasswd 1.10 default settings generate insecure passwords
Patch / fix
- makepasswd Debian 14, Debian 13, Debian 12 1.10-5
debian advisories DEBIAN-CVE-2010-2247
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2010-2247 updated cvss 3.3
makepasswd: default settin generate insecure passwords
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.33% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- makepasswd makepasswd
Classification
- Weakness
-
- CWE-1188 Initialization of a Resource with an Insecure Default
References
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/JLAGK43ZTRNAMRO7JI2AW4BAZS35QSEE/
vendor-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/HLHAXN3XRR7RJ73SJTBSW3GZT4GLHI33/
vendor-advisory
-
security-tracker.debian.org
/tracker/CVE-2010-2247
third-party-advisory
-
access.redhat.com
/security/cve/cve-2010-2247
broken-link
Sources
- CVE List CVE-2010-2247
- NVD CVE-2010-2247
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.