# CVE-2011-5240: Security feature bypass in n/a

> Magento fails to validate SSL certificates, allowing attackers to intercept traffic via man-in-the-middle attacks using valid certificates.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 6 Nov 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rgmx-whj6-vwxx

## What is CVE-2011-5240?

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

### Official description

Magento 1.5 and 1.6.2 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-5240?

It affects 1 product.


Products: Magentocommerce Magento.

## How do I fix CVE-2011-5240?

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

## Is CVE-2011-5240 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6091](https://insights.sbomify.com/CVE-2012-6091/): Information disclosure in Magento (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5240 and fix it if it is affected.

What it is: CVE-2011-5240 is a medium-severity vulnerability in n/a, published on 6 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-2011-5240 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-2011-5240/ (Markdown: https://insights.sbomify.com/CVE-2011-5240/index.md)
```

## Sources

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

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