CERTA-2011-AVI-705
Vulnerability from certfr_avis - Published: - Updated:
Des vulnérabilités dans Adobe Acrobat et Adobe Reader permettent à un utilisateur malveillant l'exécution de code arbitraire à distance.
Description
Des vulnérabilités affectent les composants en relation avec les fonctions de 3D des lecteurs PDF Adobe Reader et Acrobat Reader. Un attaquant peut les exploiter pour exécuter du code arbitraire sur le système d'un utilisateur qui ouvrirait un fichier au format PDF spécialement construit.
Solution
La version 9.4.7 de chacun des logiciels Adobe Acrobat et Adobe Reader corrige le problème.
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Adobe | Acrobat Reader | Adobe Acrobat 9.4.6 et versions 9.x antérieures pour systèmes Windows et Macintosh. | ||
| Adobe | Acrobat Reader | Adobe Reader 9.4.6 et versions 9.x antérieures pour systèmes Windows, Macintosh et UNIX ; | ||
| Adobe | Acrobat Reader | Adobe Acrobat X (10.1.1) et versions 10.x antérieures pour systèmes Windows et Macintosh ; | ||
| Adobe | Acrobat Reader | Adobe Reader X (10.1.1) et versions 10.x antérieures pour systèmes Windows et Macintosh ; |
| Title | Publication Time | Tags | |
|---|---|---|---|
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Adobe Acrobat 9.4.6 et versions 9.x ant\u00e9rieures pour syst\u00e8mes Windows et Macintosh.",
"product": {
"name": "Acrobat Reader",
"vendor": {
"name": "Adobe",
"scada": false
}
}
},
{
"description": "Adobe Reader 9.4.6 et versions 9.x ant\u00e9rieures pour syst\u00e8mes Windows, Macintosh et UNIX ;",
"product": {
"name": "Acrobat Reader",
"vendor": {
"name": "Adobe",
"scada": false
}
}
},
{
"description": "Adobe Acrobat X (10.1.1) et versions 10.x ant\u00e9rieures pour syst\u00e8mes Windows et Macintosh ;",
"product": {
"name": "Acrobat Reader",
"vendor": {
"name": "Adobe",
"scada": false
}
}
},
{
"description": "Adobe Reader X (10.1.1) et versions 10.x ant\u00e9rieures pour syst\u00e8mes Windows et Macintosh ;",
"product": {
"name": "Acrobat Reader",
"vendor": {
"name": "Adobe",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nDes vuln\u00e9rabilit\u00e9s affectent les composants en relation avec les\nfonctions de 3D des lecteurs PDF Adobe Reader et Acrobat Reader. Un\nattaquant peut les exploiter pour ex\u00e9cuter du code arbitraire sur le\nsyst\u00e8me d\u0027un utilisateur qui ouvrirait un fichier au format PDF\nsp\u00e9cialement construit.\n\n## Solution\n\nLa version 9.4.7 de chacun des logiciels Adobe Acrobat et Adobe Reader\ncorrige le probl\u00e8me.\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-2462",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-2462"
},
{
"name": "CVE-2011-4369",
"url": "https://www.cve.org/CVERecord?id=CVE-2011-4369"
}
],
"links": [
{
"title": "Bulletin d\u0027alerte Adobe apsa11-04 du 16 d\u00e9cembre 2011 :",
"url": "http://www.adobe.com/support/security/advisories/apsa11-04.html"
},
{
"title": "Document du CERTA CERTA-2011-ALE-008 du 19 d\u00e9cembre 2011 :",
"url": "http://www.certa.ssi.gouv.fr/site/CERTA-2011-ALE-008/index.html"
}
],
"reference": "CERTA-2011-AVI-705",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2011-12-19T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Des vuln\u00e9rabilit\u00e9s dans Adobe Acrobat et Adobe Reader permettent \u00e0 un\nutilisateur malveillant l\u0027ex\u00e9cution de code arbitraire \u00e0 distance.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans Adobe Reader et Acrobat Reader",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Adobe apsb11-30 du 16 d\u00e9cembre 2011",
"url": "http://www.adobe.com/support/security/bulletins/apsb11-30.html"
}
]
}
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.