CVE-2012-3372 json
The default configuration of Cyberoam UTM appliances uses the same Certification Authority certificate and same private key across differen…
published 2012-07-09 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-3345
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
The 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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 21 mo ago
Exploit prediction
0.94% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
- media.torproject.org /misc/2012-07-03-cyberoam-CVE-2012-3372.txt
- theregister.co.uk /2012/07/07/cyberoam_tor_ssl_spying_flap/
- blog.torproject.org /blog/security-vulnerability-found-cyberoam-dpi-devices-cve-2012-3372
-
archives.neohapsis.com
/archives/bugtraq/2012-07/0021.html
mailing-list
- blog.cyberoam.com /2012/07/ssl-bridging-cyberoam-approach/
Sources
- CVE List CVE-2012-3372
- NVD CVE-2012-3372
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.