# CVE-2008-3775: Weak cryptography in n/a

> Local administrators can decrypt stored passwords using weak ROT-25 encryption to access sensitive information in Folder Lock.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2008
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-h6w2-v77h-v84w

## What is CVE-2008-3775?

CVE-2008-3775 is a medium-severity vulnerability in n/a, published on 22 Aug 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Folder Lock 5.9.5 and earlier uses weak encryption (ROT-25) for the password, which allows local administrators to obtain sensitive information by reading and decrypting the QualityControl\_pack registry value.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2008-3775?

It affects 1 product.


Products: Newsoftwares Folder Lock.

## How do I fix CVE-2008-3775?

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

## Is CVE-2008-3775 being exploited?

There is no known exploitation of CVE-2008-3775 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-23039](https://insights.sbomify.com/CVE-2020-23039/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3775 and fix it if it is affected.

What it is: CVE-2008-3775 is a medium-severity vulnerability in n/a, published on 22 Aug 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-3775 in the wild and no public exploit code.

Affected product: n/a. 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-2008-3775/ (Markdown: https://insights.sbomify.com/CVE-2008-3775/index.md)
```

## Sources

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

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