# CVE-2008-2780: Information disclosure in n/a

> The Anubis encryption plugin leaks file size information in cleartext headers, allowing attackers to distinguish encrypted data from padding.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g87c-rc5c-2p9f

## What is CVE-2008-2780?

CVE-2008-2780 is a medium-severity vulnerability in n/a, published on 19 Jun 2008. 

### Official description

The Anubis (aka Anubis+Ripe160) plugin before 1.3 for encrypt stores the unencrypted file's size in cleartext in the header of the encrypted file, which allows attackers to distinguish between encrypted data and random padding at the end of the encrypted file.

Weakness: CWE-310

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

It affects 1 product.


Products: Albinoloverats Anubis Plugin.

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

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

## Is CVE-2008-2780 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2780 is a medium-severity vulnerability in n/a, published on 19 Jun 2008. 
Exploitation: There is no known exploitation of CVE-2008-2780 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-2780/ (Markdown: https://insights.sbomify.com/CVE-2008-2780/index.md)
```

## Sources

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

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