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

> Man-in-the-middle attackers can spoof SSL servers because Fortinet UTM appliances share default CA certificates and private keys across installations.

- **Severity:** Medium 5.3 (`AV:A/AC:H/Au:N/C:C/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:** 14 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p5m6-f3fp-3v88

## What is CVE-2012-4948?

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

### Official description

The default configuration of Fortinet Fortigate UTM appliances uses the same Certification Authority certificate and same private key across different customers' installations, which makes it easier for man-in-the-middle attackers to spoof SSL servers by leveraging the presence of the Fortinet_CA_SSLProxy certificate in a list of trusted root certification authorities.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 29 products.


Products: Fortinet Fortigate-1000c, Fortinet Fortigate-100d, Fortinet Fortigate-110c, Fortinet Fortigate-1240b, Fortinet Fortigate-200b, Fortinet Fortigate-20c, Fortinet Fortigate-300c, Fortinet Fortigate-3040b, Fortinet Fortigate-310b, Fortinet Fortigate-311b, Fortinet Fortigate-3140b, Fortinet Fortigate-3240c, Fortinet Fortigate-3810a, Fortinet Fortigate-3950b, Fortinet Fortigate-40c, Fortinet Fortigate-5001a-Sw, Fortinet Fortigate-5001b, Fortinet Fortigate-5020, Fortinet Fortigate-5060, Fortinet Fortigate-50b and 9 more.

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

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

## Is CVE-2012-4948 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1414](https://insights.sbomify.com/CVE-2013-1414/): Cross-site request forgery in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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