# CVE-2024-47182: Dozzle uses unsafe hash for passwords

> Dozzle uses weak SHA-256 hashing for passwords, allowing attackers to potentially recover credentials via rainbow table attacks.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Sep 2024
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-w7qr-q9fh-fj35, GO-2024-3163

## What is CVE-2024-47182?

CVE-2024-47182 is a medium-severity vulnerability in amir20 dozzle, published on 27 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-326 (Inadequate Encryption Strength), CWE-328 (Use of Weak Hash)

## Which versions are affected by CVE-2024-47182?

3 open source packages ship an affected version, including github.com/amir20/dozzle. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/amir20/dozzle` | Go | All versions | None |
| `github.com/amir20/dozzle` | Go | All versions | 8.5.3 |
| `github.com/amir20/dozzle` | Go | All versions | 8.5.3 |

Products: Amirraminfar Dozzle.

## How do I fix CVE-2024-47182?

Upgrade github.com/amir20/dozzle to 8.5.3 or later.

## Is CVE-2024-47182 being exploited?

There is no known exploitation of CVE-2024-47182 in the wild and no public exploit code.

## Other vulnerabilities in amir20 dozzle

- [CVE-2026-44985](https://insights.sbomify.com/CVE-2026-44985/): Dozzle: Cross-Site WebSocket Hijacking (CSWSH) on exec/attach endpoints bypasses authentication (high 8.7)
- [CVE-2026-24740](https://insights.sbomify.com/CVE-2026-24740/): Dozzle Agent Label-Based Access Control Bypass Allows Unauthorized Container Shell Access (high 8.7)
- [CVE-2026-45298](https://insights.sbomify.com/CVE-2026-45298/): Dozzle: Pre-auth SSRF with response-body reflection via POST /api/notifications/test-webhook (default no-auth deploy) (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47182 and fix it if it is affected.

What it is: CVE-2024-47182 is a medium-severity vulnerability in amir20 dozzle, published on 27 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47182 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/amir20/dozzle (Go): affected all versions; no fix listed
- github.com/amir20/dozzle (Go): affected all versions; fixed in 8.5.3
- github.com/amir20/dozzle (Go): affected all versions; fixed in 8.5.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47182/ (Markdown: https://insights.sbomify.com/CVE-2024-47182/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47182
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47182
- OSV: https://osv.dev/vulnerability/CVE-2024-47182

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47182/
Summaries are generated and may contain mistakes; the official description above is the record.