CERTA-2012-AVI-150

Vulnerability from certfr_avis - Published: - Updated:

Plusieurs vulnérabilités dans des produits Cisco permettent à un attaquant de provoquer un déni de service à distance.

Description

Plusieurs modules dans les produits Cisco ASA et ASASM contiennent des vulnérabilités :

  • le moteur d'inspection du trafic UDP ;
  • le moteur de recherche d'attaques (Threat Detection), non activé par défaut ;
  • le client Syslog ;
  • le gestionnaire du protocole PIM (voir l'avis CERTA-2012-AVI-149).

Ces vulnérabilités permettent à un attaquant de provoquer un déni de service à distance.

Solution

Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

None
Impacted products
Vendor Product Description
Cisco N/A Cisco Catalyst 6500 ASA Services Module.
Cisco N/A Cisco 5500 Adaptative Security Appliance (ASA) ;

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Cisco Catalyst 6500 ASA Services Module.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Cisco",
          "scada": false
        }
      }
    },
    {
      "description": "Cisco 5500 Adaptative Security Appliance (ASA) ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Cisco",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nPlusieurs modules dans les produits Cisco ASA et ASASM contiennent des\nvuln\u00e9rabilit\u00e9s\u00a0:\n\n-   le moteur d\u0027inspection du trafic UDP\u00a0;\n-   le moteur de recherche d\u0027attaques (Threat Detection), non activ\u00e9 par\n    d\u00e9faut\u00a0;\n-   le client Syslog\u00a0;\n-   le gestionnaire du protocole PIM (voir l\u0027avis CERTA-2012-AVI-149).\n\nCes vuln\u00e9rabilit\u00e9s permettent \u00e0 un attaquant de provoquer un d\u00e9ni de\nservice \u00e0 distance.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2012-0356",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-0356"
    },
    {
      "name": "CVE-2012-0355",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-0355"
    },
    {
      "name": "CVE-2012-0354",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-0354"
    },
    {
      "name": "CVE-2012-0353",
      "url": "https://www.cve.org/CVERecord?id=CVE-2012-0353"
    }
  ],
  "links": [
    {
      "title": "Document du CERTA CERTA-2012-AVI-149 du 16 mars 2012 :",
      "url": "http://www.certa.ssi.gouv.fr/site/CERTA-2012-AVI-149/index.html"
    }
  ],
  "reference": "CERTA-2012-AVI-150",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2012-03-16T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    }
  ],
  "summary": "Plusieurs vuln\u00e9rabilit\u00e9s dans des produits Cisco permettent \u00e0 un\nattaquant de provoquer un d\u00e9ni de service \u00e0 distance.\n",
  "title": "Vuln\u00e9rabilit\u00e9s dans Cisco 6500 et 5500",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Cisco 20120314-asa du 14 mars 2012",
      "url": "http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120314-asa"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.