CERTA-2011-AVI-716
Vulnerability from certfr_avis - Published: 2011-12-22 - Updated: 2011-12-22
Une vulnérabilité dans le pilote NVIDIA Stereoscopic 3D permet à une personne malveillante de prendre le contrôle total du système.
Description
Une vulnérabilité est présente dans le pilote NVIDIA Stereoscopic 3D. Ce pilote ne vérifie pas correctement les commandes envoyées à un canal nommé (named pipe). Cette vulnérabilité peut être exploitée par une personne malveillante pour exécuter des commandes arbitraires dans le contexte du compte LocalSystem et ainsi prendre le contrôle total de la machine. Toutefois, l'attaquant doit posséder des identifiants valides et pouvoir se connecter en local sur la machine.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
Pilote NVIDIA Stereoscopic 3D pour Windows.
| Vendor | Product | Description |
|---|
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [],
"affected_systems_content": "\u003cP\u003ePilote NVIDIA \u003cSPAN class=\"textit\"\u003eStereoscopic 3D\u003c/SPAN\u003e pour Windows.\u003c/P\u003e",
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 est pr\u00e9sente dans le pilote NVIDIA Stereoscopic 3D. Ce\npilote ne v\u00e9rifie pas correctement les commandes envoy\u00e9es \u00e0 un canal\nnomm\u00e9 (named pipe). Cette vuln\u00e9rabilit\u00e9 peut \u00eatre exploit\u00e9e par une\npersonne malveillante pour ex\u00e9cuter des commandes arbitraires dans le\ncontexte du compte LocalSystem et ainsi prendre le contr\u00f4le total de la\nmachine. Toutefois, l\u0027attaquant doit poss\u00e9der des identifiants valides\net pouvoir se connecter en local sur la machine.\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-2011-4784",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-4784"
}
],
"initial_release_date": "2011-12-22T00:00:00",
"last_revision_date": "2011-12-22T00:00:00",
"links": [
{
"title": "T\u00e9l\u00e9chargement des derniers pilotes NVIDIA :",
"url": "http://www.nvidia.com/Download/index.aspx"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MSVR11-016 du 20 d\u00e9cembre 2011 :",
"url": "http://technet.microsoft.com/en-us/security/msvr/MSVR11-016"
}
],
"reference": "CERTA-2011-AVI-716",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-12-22T00:00:00.000000"
}
],
"risks": [
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": "Une vuln\u00e9rabilit\u00e9 dans le pilote NVIDIA \u003cspan\nclass=\"textit\"\u003eStereoscopic 3D\u003c/span\u003e permet \u00e0 une personne malveillante\nde prendre le contr\u00f4le total du syst\u00e8me.\n",
"title": "Vuln\u00e9rabilit\u00e9 dans le pilote NVIDIA Stereoscopic 3D",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MSVR11-016 du 20 d\u00e9cembre 2011",
"url": null
}
]
}
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.