CERTA-2009-AVI-328
Vulnerability from certfr_avis - Published: 2009-08-12 - Updated: 2009-08-12
Une vulnérabilité a été identifiée dans le service de mise en file d'attente MSMQ de Microsoft Windows. Un utilisateur local peut chercher à l'exploiter pour élever ses privilèges.
Description
Une vulnérabilité a été identifiée dans le service de mise en file d'attente MSMQ de Microsoft Windows. Le service vérifie de façon incorrecte les données en entrée avant de les transmettre au tampon. Le service n'est cependant pas activé par défaut. Dans le cas contraire, une personne peut chercher à exploiter cette vulnérabilité afin d'élever ses privilèges locaux.
Solution
Se référer au bulletin de sécurité MS09-040 de Microsoft pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Microsoft | Windows | Windows Server 2003 Édition x64 Service Pack 2 ; | ||
| Microsoft | Windows | Windows Server 2003 avec SP2 pour systèmes Itanium ; | ||
| Microsoft | Windows | Windows XP Service Pack 2 ; | ||
| Microsoft | Windows | Windows XP Professionnel Édition x64 Service Pack 2 ; | ||
| Microsoft | Windows | Windows Vista Édition x64. | ||
| Microsoft | Windows | Windows Server 2003 Service Pack 2 ; | ||
| Microsoft | Windows | Windows Vista ; | ||
| Microsoft | Windows | Microsoft Windows 2000 Service Pack 4 ; |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Windows Server 2003 \u00c9dition x64 Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Server 2003 avec SP2 pour syst\u00e8mes Itanium ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows XP Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows XP Professionnel \u00c9dition x64 Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Vista \u00c9dition x64.",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Server 2003 Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Vista ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Windows 2000 Service Pack 4 ;",
"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 service de mise en file\nd\u0027attente MSMQ de Microsoft Windows. Le service v\u00e9rifie de fa\u00e7on\nincorrecte les donn\u00e9es en entr\u00e9e avant de les transmettre au tampon. Le\nservice n\u0027est cependant pas activ\u00e9 par d\u00e9faut. Dans le cas contraire,\nune personne peut chercher \u00e0 exploiter cette vuln\u00e9rabilit\u00e9 afin d\u0027\u00e9lever\nses privil\u00e8ges locaux.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 MS09-040 de Microsoft pour\nl\u0027obtention des correctifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2009-1922",
"url": "https://www.cve.org/CVERecord?id=CVE-2009-1922"
}
],
"initial_release_date": "2009-08-12T00:00:00",
"last_revision_date": "2009-08-12T00:00:00",
"links": [],
"reference": "CERTA-2009-AVI-328",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2009-08-12T00:00:00.000000"
}
],
"risks": [
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 identifi\u00e9e dans le service de mise en file\nd\u0027attente MSMQ de Microsoft Windows. Un utilisateur local peut chercher\n\u00e0 l\u0027exploiter pour \u00e9lever ses privil\u00e8ges.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans le service MSMQ Microsoft Windows",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS09-040 du 11 ao\u00fbt 2009",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS09-040.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.