CERTA-2008-AVI-080
Vulnerability from certfr_avis - Published: 2008-02-13 - Updated: 2008-02-13
Une vulnérabilité a été identifiée dans le traitement de réponses DHCP par le système Microsoft Windows Vista. Elle pourrait être exploitée par une personne malveillante afin de perturber les couches protocolaires et éventuellement redémarrer le système.
Description
Une vulnérabilité a été identifiée dans le traitement de réponses DHCP par le système Microsoft Windows Vista. DHCP, ou Dynamic Host Configuration Protocol, est le protocole utilisé par différents éléments réseau afin d'obtenir les informations nécessaires à leur fonctionnement (adresse IP disponible, adresse des serveurs DNS et passerelles associées, etc.).
Le système d'exploitation ne gère pas correctement certaines réponses retournées par un serveur DHCP. Une personne malveillante pourrait ainsi forger de telles réponses afin de perturber les couches protocolaires et éventuellement forcer les systèmes en attente de réponse à redémarrer.
Solution
Se référer au bulletin de sécurité MS08-004 de Microsoft pour l'obtention des correctifs (cf. section Documentation).
None| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Windows Vista Edition x64.",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Vista ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans le traitement de r\u00e9ponses DHCP\npar le syst\u00e8me Microsoft Windows Vista. DHCP, ou Dynamic Host\nConfiguration Protocol, est le protocole utilis\u00e9 par diff\u00e9rents \u00e9l\u00e9ments\nr\u00e9seau afin d\u0027obtenir les informations n\u00e9cessaires \u00e0 leur fonctionnement\n(adresse IP disponible, adresse des serveurs DNS et passerelles\nassoci\u00e9es, etc.).\n\nLe syst\u00e8me d\u0027exploitation ne g\u00e8re pas correctement certaines r\u00e9ponses\nretourn\u00e9es par un serveur DHCP. Une personne malveillante pourrait ainsi\nforger de telles r\u00e9ponses afin de perturber les couches protocolaires et\n\u00e9ventuellement forcer les syst\u00e8mes en attente de r\u00e9ponse \u00e0 red\u00e9marrer.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 MS08-004 de Microsoft pour\nl\u0027obtention des correctifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2008-0084",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-0084"
}
],
"initial_release_date": "2008-02-13T00:00:00",
"last_revision_date": "2008-02-13T00:00:00",
"links": [],
"reference": "CERTA-2008-AVI-080",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2008-02-13T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans le traitement de r\u00e9ponses DHCP\npar le syst\u00e8me Microsoft Windows Vista. Elle pourrait \u00eatre exploit\u00e9e par\nune personne malveillante afin de perturber les couches protocolaires et\n\u00e9ventuellement red\u00e9marrer le syst\u00e8me.\n",
"title": "Vuln\u00e9rabilit\u00e9 du traitement DHCP par Windows Vista",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS08-004 du 12 f\u00e9vrier 2008",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS08-004.mspx"
}
]
}
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.
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
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.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.