CERTA-2006-AVI-347

Vulnerability from certfr_avis - Published: 2006-08-09 - Updated: 2006-09-28

None

Description

Une vulnérabilité de nature non-précisée par l'éditeur est présente dans le noyau du système d'exploitation Windows 2000. Elle permet à un utilisateur local d'élever ses privilèges.

La mise à jour publiée le 08 août 2006 semble introduire quelques problèmes dont une vulnérabilité critique, pouvant permettre à un utilisateur local d'élever ses privilèges et prendre le contrôle du système vulnérable.

Solution

Se référer au dernier bulletin de sécurité de l'éditeur publié le 26 septembre 2006 pour l'obtention des correctifs (cf. section Documentation).

Windows 2000 Service Pack 4.

Impacted products
Vendor Product Description

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cp\u003eWindows 2000 Service Pack 4.\u003c/p\u003e",
  "content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 de nature non-pr\u00e9cis\u00e9e par l\u0027\u00e9diteur est pr\u00e9sente dans\nle noyau du syst\u00e8me d\u0027exploitation Windows 2000. Elle permet \u00e0 un\nutilisateur local d\u0027\u00e9lever ses privil\u00e8ges.\n\nLa mise \u00e0 jour publi\u00e9e le 08 ao\u00fbt 2006 semble introduire quelques\nprobl\u00e8mes dont une vuln\u00e9rabilit\u00e9 critique, pouvant permettre \u00e0 un\nutilisateur local d\u0027\u00e9lever ses privil\u00e8ges et prendre le contr\u00f4le du\nsyst\u00e8me vuln\u00e9rable.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au dernier bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur publi\u00e9 le 26\nseptembre 2006 pour l\u0027obtention des correctifs (cf. section\nDocumentation).\n",
  "cves": [
    {
      "name": "CVE-2006-3444",
      "url": "https://www.cve.org/CVERecord?id=CVE-2006-3444"
    }
  ],
  "initial_release_date": "2006-08-09T00:00:00",
  "last_revision_date": "2006-09-28T00:00:00",
  "links": [
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-049 du 09 ao\u00fbt 2006    remis \u00e0 jour le 26 septembre 2006 :",
      "url": "http://www.microsoft.com/technet/security/Bulletin/MS06-aug.mspx"
    },
    {
      "title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-049 du 09 ao\u00fbt 2006    remis \u00e0 jour le 26 septembre 2006 :",
      "url": "http://www.microsoft.com/france/technet/security/Bulletin/MS06-049.mspx"
    }
  ],
  "reference": "CERTA-2006-AVI-347",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2006-08-09T00:00:00.000000"
    },
    {
      "description": "ajout de la r\u00e9f\u00e9rence CVE et de la nouvelle mise \u00e0 jour du bulletin MS06-049.",
      "revision_date": "2006-09-28T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "\u00c9l\u00e9vation de privil\u00e8ges"
    }
  ],
  "summary": null,
  "title": "Vuln\u00e9rabilit\u00e9 du noyau de Windows 2000",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS06-049 du 8 ao\u00fbt 2006",
      "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.