# CVE-2010-3074: Weak cryptography in n/a

> Local attackers can exploit weak AES-CBC encryption in EncFS to recover sensitive data from encrypted filesystems via watermark attacks.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-3074, GHSA-2r66-g66j-95vv

## What is CVE-2010-3074?

CVE-2010-3074 is a low-severity vulnerability in n/a, published on 17 Sep 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SSL_Cipher.cpp in EncFS before 1.7.0 uses an improper combination of an AES cipher and a CBC cipher mode for encrypted filesystems, which allows local users to obtain sensitive information via a watermark attack.

Weakness: CWE-310

## Which versions are affected by CVE-2010-3074?

It affects 1 product.


Products: Arg0 Encfs.

## How do I fix CVE-2010-3074?

Upgrade to a fixed version.

## Is CVE-2010-3074 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-3075](https://insights.sbomify.com/CVE-2010-3075/): Weak cryptography in n/a (medium 5.0)
- [CVE-2010-3073](https://insights.sbomify.com/CVE-2010-3073/): Weak cryptography in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3074 and fix it if it is affected.

What it is: CVE-2010-3074 is a low-severity vulnerability in n/a, published on 17 Sep 2010. 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-2010-3074 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-2010-3074/ (Markdown: https://insights.sbomify.com/CVE-2010-3074/index.md)
```

## Sources

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

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