CERTA-2006-AVI-444

Vulnerability from certfr_avis - Published: 2006-10-11 - Updated: 2006-10-11

Trois vulnérabilités affectant la mise en oeuvre d'IPv6 sous Windows permettent de réaliser des dénis de service à distance.

Description

Trois vulnérabilités affectant la mise en oeuvre d'IPv6 sous Windows ont été découvertes. Il s'agit d'anciennes vulnérabilités qui avaient fait l'objet d'un avis du CERTA (CERTA-2005-AVI-135) et qui avaient été corrigées par Microsoft pour IPv4 seulement (bulletin de sécurité MS05-019). Ces vulnérabilités permettent de mettre fin à une connexion TCP établie ou de l'ignorer (CVE-2004-0790 et CVE-2004-0230) et d'entraîner une consommation excessive des ressources CPU (CVE-2005-0688).

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
Microsoft Windows Microsoft Windows XP Professional x64 Edition ;
Microsoft Windows Microsoft Windows Server 2003 (Itanium) et Microsoft Windows Server 2003 Service Pack 1 (Itanium) ;
Microsoft Windows Microsoft Windows Server 2003 et Microsoft Windows Server 2003 Service Pack 1 ;
Microsoft Windows Microsoft Windows XP Service Pack 1 et Service Pack 2 ;
Microsoft Windows Microsoft Windows Server 2003 x64 Edition.

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Microsoft Windows XP Professional x64 Edition ;",
      "product": {
        "name": "Windows",
        "vendor": {
          "name": "Microsoft",
          "scada": false
        }
      }
    },
    {
      "description": "Microsoft Windows Server 2003 (Itanium) et Microsoft Windows Server 2003 Service Pack 1 (Itanium) ;",
      "product": {
        "name": "Windows",
        "vendor": {
          "name": "Microsoft",
          "scada": false
        }
      }
    },
    {
      "description": "Microsoft Windows Server 2003 et Microsoft Windows Server 2003 Service Pack 1 ;",
      "product": {
        "name": "Windows",
        "vendor": {
          "name": "Microsoft",
          "scada": false
        }
      }
    },
    {
      "description": "Microsoft Windows XP Service Pack 1 et Service Pack 2 ;",
      "product": {
        "name": "Windows",
        "vendor": {
          "name": "Microsoft",
          "scada": false
        }
      }
    },
    {
      "description": "Microsoft Windows Server 2003 x64 Edition.",
      "product": {
        "name": "Windows",
        "vendor": {
          "name": "Microsoft",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nTrois vuln\u00e9rabilit\u00e9s affectant la mise en oeuvre d\u0027IPv6 sous Windows ont\n\u00e9t\u00e9 d\u00e9couvertes. Il s\u0027agit d\u0027anciennes vuln\u00e9rabilit\u00e9s qui avaient fait\nl\u0027objet d\u0027un avis du CERTA (CERTA-2005-AVI-135) et qui avaient \u00e9t\u00e9\ncorrig\u00e9es par Microsoft pour IPv4 seulement (bulletin de s\u00e9curit\u00e9\nMS05-019). Ces vuln\u00e9rabilit\u00e9s permettent de mettre fin \u00e0 une connexion\nTCP \u00e9tablie ou de l\u0027ignorer (CVE-2004-0790 et CVE-2004-0230) et\nd\u0027entra\u00eener une consommation excessive des ressources CPU\n(CVE-2005-0688).\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-2004-0230",
      "url": "https://www.cve.org/CVERecord?id=CVE-2004-0230"
    },
    {
      "name": "CVE-2005-0688",
      "url": "https://www.cve.org/CVERecord?id=CVE-2005-0688"
    },
    {
      "name": "CVE-2004-0790",
      "url": "https://www.cve.org/CVERecord?id=CVE-2004-0790"
    }
  ],
  "initial_release_date": "2006-10-11T00:00:00",
  "last_revision_date": "2006-10-11T00:00:00",
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS05-019 du 12 avril 2005 :",
      "url": "http://www.microsoft.com/technet/security/Bulletin/MS05-019.mspx"
    },
    {
      "title": "Avis CERTA-2005-AVI-135 du 13 avril 2005 :",
      "url": "http://www.certa.ssi.gouv.fr/site/CERTA-2005-AVI-135/index.html"
    }
  ],
  "reference": "CERTA-2006-AVI-444",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2006-10-11T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service \u00e0 distance"
    }
  ],
  "summary": "Trois vuln\u00e9rabilit\u00e9s affectant la mise en oeuvre d\u0027IPv6 sous Windows\npermettent de r\u00e9aliser des d\u00e9nis de service \u00e0 distance.\n",
  "title": "Vuln\u00e9rabilit\u00e9s dans la gestion d\u0027IPv6 sous Windows",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-064 du 10 octobre 2006",
      "url": "http://www.microsoft.com/france/technet/security/Bulletin/MS06-064.mspx"
    }
  ]
}



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.