# CVE-2024-36497: Unhashed Storage of Password

> Attackers can extract cleartext passwords from configuration files to bypass security restrictions and disable the application.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-7p6q-hqg2-6cpg

## What is CVE-2024-36497?

CVE-2024-36497 is a critical vulnerability in Faronics WINSelect (Standard + Enterprise), published on 24 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The decrypted configuration file contains the password in cleartext 
which is used to configure WINSelect. It can be used to remove the 
existing restrictions and disable WINSelect entirely.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

No fix has been published for CVE-2024-36497 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-36497 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36497 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36497 is a critical vulnerability in Faronics WINSelect (Standard + Enterprise), published on 24 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36497 exists.

Affected product: Faronics WINSelect (Standard + Enterprise). No package-level version data is available, so check the vendor advisory linked from the reference page.

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-36497/ (Markdown: https://insights.sbomify.com/CVE-2024-36497/index.md)
```

## Sources

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

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