CERTA-2010-AVI-485
Vulnerability from certfr_avis - Published: 2010-10-13 - Updated: 2010-10-13
Une vulnérabilité présente dans le service de partage réseau de Microsoft Windows Media Player permet à un utilisateur d'exécuter du code arbitraire à distance. La configuration par défaut de ce service rend cette vulnérabilité exploitable uniquement depuis le réseau local.
Description
Une vulnérabilité a été identifiée dans le service de partage réseau du lecteur multimédia Windows Media Player. La réception d'un paquet RTSP spécialement conçu peut provoquer une exécution de code à distance.
En configuration par défaut, cette attaque ne peut être menée que depuis le réseau local. Sur les systèmes Windows Vista, Windows 7 professionnel, entreprise et ultimate, le service de partage n'est pas activé par défaut. Par contre, il est en service sur les autres versions de Windows 7.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Microsoft | Windows | Windows Media Player sur Windows Vista Service Pack 1 et Service Pack 2 ; | ||
| Microsoft | Windows | Windows Media Player sur Windows 7 pour les systèmes 32 bits ; | ||
| Microsoft | Windows | Windows Media Player sur Windows 7 pour les systèmes 64 bits. | ||
| Microsoft | Windows | Windows Media Player sur Windows Vista x64 Edition Service Pack 1 et Service Pack 2 ; |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Windows Media Player sur Windows Vista Service Pack 1 et Service Pack 2 ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Media Player sur Windows 7 pour les syst\u00e8mes 32 bits ;",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Media Player sur Windows 7 pour les syst\u00e8mes 64 bits.",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Windows Media Player sur Windows Vista x64 Edition Service Pack 1 et Service Pack 2 ;",
"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 partage r\u00e9seau du\nlecteur multim\u00e9dia Windows Media Player. La r\u00e9ception d\u0027un paquet RTSP\nsp\u00e9cialement con\u00e7u peut provoquer une ex\u00e9cution de code \u00e0 distance.\n\nEn configuration par d\u00e9faut, cette attaque ne peut \u00eatre men\u00e9e que depuis\nle r\u00e9seau local. Sur les syst\u00e8mes Windows Vista, Windows 7\nprofessionnel, entreprise et ultimate, le service de partage n\u0027est pas\nactiv\u00e9 par d\u00e9faut. Par contre, il est en service sur les autres versions\nde Windows 7.\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-2010-3225",
"url": "https://www.cve.org/CVERecord?id=CVE-2010-3225"
}
],
"initial_release_date": "2010-10-13T00:00:00",
"last_revision_date": "2010-10-13T00:00:00",
"links": [],
"reference": "CERTA-2010-AVI-485",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2010-10-13T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 pr\u00e9sente dans le service de partage r\u00e9seau de\nMicrosoft Windows Media Player permet \u00e0 un utilisateur d\u0027ex\u00e9cuter du\ncode arbitraire \u00e0 distance. La configuration par d\u00e9faut de ce service\nrend cette vuln\u00e9rabilit\u00e9 exploitable uniquement depuis le r\u00e9seau local.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans le service de partage r\u00e9seau de Media Player",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS10-075 du 12 octobre 2010",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS10-075.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.