CVE-2024-47182 json
Dozzle uses unsafe hash for passwords
published 2024-09-27 2 y ago modified 2026-06-17 4 mo ago also GHSA-w7qr-q9fh-fj35 , GO-2024-3163 , EUVD-2024-3150
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
Dozzle is a realtime log viewer for docker containers. Before version 8.5.3, the app uses sha-256 as the hash for passwords, which leaves users susceptible to rainbow table attacks. The app switches to bcrypt, a more appropriate hash for passwords, in version 8.5.3.
Patch / fix
- go github.com/amir20/dozzle 8.5.3
- amirraminfar dozzle 8.5.3
- govulncheck-vulndb SLE Module for Package Hub 15 SP6, SLE Module for Package Hub 15 SP5, openSUSE Leap 15.6 +1 more 0.0.20241030T212825-150000.1.9.1
suse advisories SUSE-SU-2024:3911-1
- govulncheck-vulndb Package Hub 12 0.0.20241104T154416-5.1
- govulncheck-vulndb openSUSE Tumbleweed 0.0.20241030T212825-1.1
opensuse advisories openSUSE-SU-2024:0350-1openSUSE-SU-2024:14447-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/amir20/dozzle | <8.5.3 all versions |
8.5.3 |
Affected products
- amir20 dozzle
Classification
References
Sources
- CVE List CVE-2024-47182
- GitHub Advisory GHSA-w7qr-q9fh-fj35
- NVD CVE-2024-47182
- OSV GO-2024-3163
Fencer Vulns 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.