Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-w7qr-q9fh-fj35

MEDIUMFix: amir20/dozzle@de79f03

GHSA-w7qr-q9fh-fj35 is a medium-severity (CVSS 4.8) CWE-328 vulnerability in github.com/amir20/dozzle. O3 Security confirms whether GHSA-w7qr-q9fh-fj35 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Dozzle uses unsafe hash for passwords

Also known asCVE-2024-47182GO-2024-3163
Published
Oct 9, 2024
Updated
Oct 9, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected
🐹github.com/amir20/dozzle

Real-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:

PoC

N/A

Impact

It leaves users susceptible to rainbow table attacks

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/amir20/dozzleall versions8.5.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/amir20/dozzle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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 GHSA-w7qr-q9fh-fj35 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-w7qr-q9fh-fj35 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w7qr-q9fh-fj35. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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-
O3 Security · Impact-Aware SCA

Is GHSA-w7qr-q9fh-fj35 in your dependencies?

O3 detects GHSA-w7qr-q9fh-fj35 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.