CVE-2024-47182 is a medium-severity (CVSS 4.8) CWE-328 vulnerability in github.com/amir20/dozzle. A fix is available for github.com/amir20/dozzle — see the affected versions and patch details below.
Dozzle uses unsafe hash for passwords
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-47182.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/amir20/dozzleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The app uses sha-256 as the hash for passwords. The app should switch to bcrypt.
Details
SHA-256 is a message digest hash, and not classified as secure for password hashing. Message digest hashes are designed to be fast, while password hashing mechanisms are designed with certain cryptographic properties (e.g. slow) to protect against vulnerabilities. Refer to the links below for more information:
- https://security.stackexchange.com/questions/195563/why-is-sha-256-not-good-for-passwords
- https://stackoverflow.com/questions/11624372/best-practice-for-hashing-passwords-sha256-or-sha512
- https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html#pre-hashing-passwords-with-bcrypt
PoC
N/A
Impact
It leaves users susceptible to rainbow table attacks
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/amir20/dozzle | all versions | 8.5.3go get github.com/amir20/dozzle@v8.5.3 |
Affected Products
dozzleamirraminfarDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/amir20/dozzle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/amir20/dozzle to 8.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47182 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Frequently Asked Questions
Is CVE-2024-47182 in your dependencies?
Find it across Go, including transitive dependencies.