CVE-2012-3372
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe default configuration of Cyberoam 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 Cyberoam_SSL_CA certificate in a list of trusted root certification authorities. NOTE: the vendor disputes the significance of this issue because the appliance "does not allow import or export of the foresaid private key.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCyberoam UTM appliances ship with a default CA certificate and private key that is identical across all customer installations. This means the Cyberoam_SSL_CA root certificate installed on multiple networks uses the same private key, allowing anyone with this key to perform SSL/TLS man-in-the-middle attacks and spoof any SSL-protected server on any affected installation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Cyberoam UTM installationReview your network infrastructure to determine if Cyberoam Unified Threat Management appliances or virtual appliances are deployed for gateway security, SSL inspection, or threat management.Affected if Cyberoam UTM is present in the environment
-
Locate the SSL inspection CA certificateAccess the Cyberoam UTM admin console or command-line interface and navigate to the SSL inspection or CA certificate management section. Identify the root CA certificate configured for SSL/TLS inspection.Affected if A CA certificate named 'Cyberoam_SSL_CA' is configured as the SSL inspection authority
-
Verify the certificate is the default shared oneExport or view the CA certificate details including issuer, subject, serial number, and validity dates. Check whether this certificate matches the factory-default CA distributed with Cyberoam appliances.Affected if The installed CA certificate is the original default certificate shipped with the appliance and has not been replaced with a unique per-installation certificate
-
Confirm SSL inspection is enabledCheck the proxy or SSL inspection settings to determine if SSL/TLS interception is actively enabled on the appliance.Affected if SSL inspection is enabled and using the default Cyberoam_SSL_CA certificate
You are affected if Cyberoam UTM is deployed with SSL inspection enabled and the default shared Cyberoam_SSL_CA certificate with the well-known private key is still in use rather than a unique certificate generated for your installation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataGenerate and deploy unique CA certificates and private keys for each customer installation, then re-establish trust on all SSL-inspected clients by replacing the shared default certificate with the new unique certificate.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3372 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3372 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data