CERTA-2011-AVI-469

Vulnerability from certfr_avis - Published: 2011-08-25 - Updated: 2011-08-25

Une vulnérabilité permettant à une personne malintentionnée d'effectuer un déni de service à distance a été découverte dans Cisco IOS.

Description

Une vulnérabilité a été découverte dans Cisco IOS. Elle permet à une personne malintentionnée d'effectuer un déni de service à distance lors de l'établissment de deux connexions ssh2. Bien que la cause exacte de cette faille ne soit pas connue, l'éditeur précise qu'elle est liée à l'utilisation de bannières personnalisées.

Solution

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

Cisco IOS 12.x.

Impacted products
Vendor Product Description
References

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cp\u003eCisco IOS 12.x.\u003c/p\u003e",
  "content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 d\u00e9couverte dans Cisco IOS. Elle permet \u00e0 une\npersonne malintentionn\u00e9e d\u0027effectuer un d\u00e9ni de service \u00e0 distance lors\nde l\u0027\u00e9tablissment de deux connexions ssh2. Bien que la cause exacte de\ncette faille ne soit pas connue, l\u0027\u00e9diteur pr\u00e9cise qu\u0027elle est li\u00e9e \u00e0\nl\u0027utilisation de banni\u00e8res personnalis\u00e9es.\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-2011-1624",
      "url": "https://www.cve.org/CVERecord?id=CVE-2011-1624"
    }
  ],
  "initial_release_date": "2011-08-25T00:00:00",
  "last_revision_date": "2011-08-25T00:00:00",
  "links": [
    {
      "title": "Notes de mise \u00e0 jour Cisco du    04 ao\u00fbt 2011 :",
      "url": "http://www.cisco.com/en/US/docs/switches/lan/cisco_ie3000/software/release/12.2_58_se/release/notes/OL24335.html"
    }
  ],
  "reference": "CERTA-2011-AVI-469",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2011-08-25T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    }
  ],
  "summary": "Une vuln\u00e9rabilit\u00e9 permettant \u00e0 une personne malintentionn\u00e9e d\u0027effectuer\nun d\u00e9ni de service \u00e0 distance a \u00e9t\u00e9 d\u00e9couverte dans \u003cspan\nclass=\"textit\"\u003eCisco IOS\u003c/span\u003e.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans Cisco IOS",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Notes de mise \u00e0 jour Cisco du 04 ao\u00fbt 2011",
      "url": null
    }
  ]
}



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.