GSD-2012-3372

Vulnerability from gsd - Updated: 2023-12-13 01:20
Details
** DISPUTED ** 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."
Aliases
Aliases
CVE-2012-3372
To clipboard 

{
  "GSD": {
    "alias": "CVE-2012-3372",
    "description": "** DISPUTED ** The default configuration of Cyberoam UTM appliances uses the same Certification Authority certificate and same private key across different customers\u0027 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.\"",
    "id": "GSD-2012-3372"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2012-3372"
      ],
      "details": "** DISPUTED ** The default configuration of Cyberoam UTM appliances uses the same Certification Authority certificate and same private key across different customers\u0027 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.\"",
      "id": "GSD-2012-3372",
      "modified": "2023-12-13T01:20:20.095588Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "secalert@redhat.com",
        "ID": "CVE-2012-3372",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "n/a",
                    "version": {
                      "version_data": [
                        {
                          "version_value": "n/a"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "n/a"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "** DISPUTED ** The default configuration of Cyberoam UTM appliances uses the same Certification Authority certificate and same private key across different customers\u0027 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.\""
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "n/a"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://media.torproject.org/misc/2012-07-03-cyberoam-CVE-2012-3372.txt",
            "refsource": "MISC",
            "url": "https://media.torproject.org/misc/2012-07-03-cyberoam-CVE-2012-3372.txt"
          },
          {
            "name": "http://www.theregister.co.uk/2012/07/07/cyberoam_tor_ssl_spying_flap/",
            "refsource": "MISC",
            "url": "http://www.theregister.co.uk/2012/07/07/cyberoam_tor_ssl_spying_flap/"
          },
          {
            "name": "https://blog.torproject.org/blog/security-vulnerability-found-cyberoam-dpi-devices-cve-2012-3372",
            "refsource": "MISC",
            "url": "https://blog.torproject.org/blog/security-vulnerability-found-cyberoam-dpi-devices-cve-2012-3372"
          },
          {
            "name": "20120703 Cyberoam advisory",
            "refsource": "BUGTRAQ",
            "url": "http://archives.neohapsis.com/archives/bugtraq/2012-07/0021.html"
          },
          {
            "name": "http://blog.cyberoam.com/2012/07/ssl-bridging-cyberoam-approach/",
            "refsource": "MISC",
            "url": "http://blog.cyberoam.com/2012/07/ssl-bridging-cyberoam-approach/"
          }
        ]
      }
    },
    "nvd.nist.gov": {
      "cve": {
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:h:elitecore:cyberoam_unified_threat_management:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "9F6D1E67-3012-4230-AAA8-3770ADC6BD0C",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "descriptions": [
          {
            "lang": "en",
            "value": "The default configuration of Cyberoam UTM appliances uses the same Certification Authority certificate and same private key across different customers\u0027 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."
          },
          {
            "lang": "es",
            "value": "** EN DISPUTA ** La configuraci\u00f3n por defecto del dispositivo Cyberoam UTM utiliza la misma clave privada en distintas instalaciones de clientes, lo que que facilita a atacantes MITM (man-in-the-Middle u hombre-en-medio) a espiar servidores SSL aprovechando la presencia del certificado Cyberoam_SSL_CA en una lista de confianza de autoridades emisoras de certificados ra\u00edz. NOTA: el vendedor se opone a la importancia de esta cuesti\u00f3n, porque el dispositivo \"no permite la importaci\u00f3n o exportaci\u00f3n de la mencionada clave privada\""
          }
        ],
        "id": "CVE-2012-3372",
        "lastModified": "2024-04-11T00:49:07.093",
        "metrics": {
          "cvssMetricV2": [
            {
              "acInsufInfo": false,
              "baseSeverity": "MEDIUM",
              "cvssData": {
                "accessComplexity": "MEDIUM",
                "accessVector": "NETWORK",
                "authentication": "NONE",
                "availabilityImpact": "NONE",
                "baseScore": 5.8,
                "confidentialityImpact": "PARTIAL",
                "integrityImpact": "PARTIAL",
                "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:N",
                "version": "2.0"
              },
              "exploitabilityScore": 8.6,
              "impactScore": 4.9,
              "obtainAllPrivilege": false,
              "obtainOtherPrivilege": false,
              "obtainUserPrivilege": false,
              "source": "nvd@nist.gov",
              "type": "Primary",
              "userInteractionRequired": true
            }
          ]
        },
        "published": "2012-07-09T10:20:44.417",
        "references": [
          {
            "source": "secalert@redhat.com",
            "url": "http://archives.neohapsis.com/archives/bugtraq/2012-07/0021.html"
          },
          {
            "source": "secalert@redhat.com",
            "url": "http://blog.cyberoam.com/2012/07/ssl-bridging-cyberoam-approach/"
          },
          {
            "source": "secalert@redhat.com",
            "url": "http://www.theregister.co.uk/2012/07/07/cyberoam_tor_ssl_spying_flap/"
          },
          {
            "source": "secalert@redhat.com",
            "url": "https://blog.torproject.org/blog/security-vulnerability-found-cyberoam-dpi-devices-cve-2012-3372"
          },
          {
            "source": "secalert@redhat.com",
            "url": "https://media.torproject.org/misc/2012-07-03-cyberoam-CVE-2012-3372.txt"
          }
        ],
        "sourceIdentifier": "secalert@redhat.com",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-310"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.