# CVE-2012-5822: Security feature bypass in n/a

> Man-in-the-middle attackers can spoof SSL servers in Zamboni due to missing hostname verification in certificate validation.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/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:** 4 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x3vm-975q-mg2x

## What is CVE-2012-5822?

CVE-2012-5822 is a high-severity vulnerability in n/a, published on 4 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The contribution feature in Zamboni does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate, related to use of the Python urllib2 library.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Mozilla Zamboni.

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

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

## Is CVE-2012-5822 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5822 is a high-severity vulnerability in n/a, published on 4 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-5822 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-5822/ (Markdown: https://insights.sbomify.com/CVE-2012-5822/index.md)
```

## Sources

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

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