LiveActive security incident?Get immediate response
CVE Record

CVE-2012-4948: The default configuration of Fortinet Fortigate UTM appliances uses the same Certification Authority certif...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Fortinet Fortigate UTM appliances reportedly shipped with a default SSL proxy CA certificate and private key shared across customer installations. If that CA is trusted by user devices, an attacker in a network interception position could more easily impersonate SSL-protected servers. Exposure is most likely where Fortigate UTM SSL inspection/proxy features used the default Fortinet_CA_SSLProxy CA and where endpoints trusted that CA as a root authority. The supplied data does not identify exact versions or deployment scope. Treat this as a trust-boundary issue for environments using Fortigate SSL inspection. Prioritize validation over emergency response unless your organization confirms affected default CA trust is still present. Mitigation focus: Check Fortinet and CERT guidance for official remediation details.; Identify Fortigate appliances using SSL proxy or SSL inspection.; Replace default/shared CA material with organization-controlled unique trust material if vendor guidance supports it..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2012-4948 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.