# CVE-2012-2405: Weak cryptography in n/a

> Gallery software has improper encryption implementation, potentially exposing data or allowing unauthorized access.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 22 Apr 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vh5f-mhcm-54fp

## What is CVE-2012-2405?

CVE-2012-2405 is a critical vulnerability in n/a, published on 22 Apr 2012. It can be exploited over the network.

### Official description

Gallery 2 before 2.3.2 and 3 before 3.0.3 does not properly implement encryption, which has unspecified impact and attack vectors, a different vulnerability than CVE-2012-1113.

Weakness: CWE-310

## Which versions are affected by CVE-2012-2405?

It affects 2 products.


Products: Maian Gallery, Menalto Gallery.

## How do I fix CVE-2012-2405?

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

## Is CVE-2012-2405 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2076](https://insights.sbomify.com/CVE-2007-2076/): Code injection in n/a (medium 6.8)
- [CVE-2012-1113](https://insights.sbomify.com/CVE-2012-1113/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2405 and fix it if it is affected.

What it is: CVE-2012-2405 is a critical vulnerability in n/a, published on 22 Apr 2012. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2012-2405 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-2012-2405/ (Markdown: https://insights.sbomify.com/CVE-2012-2405/index.md)
```

## Sources

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

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