CERTA-2007-AVI-291
Vulnerability from certfr_avis - Published: 2007-07-11 - Updated: 2007-07-11None
Description
Plusieurs vulnérabilités ont été identifiées dans l'application Excel de la suite bureautique Microsoft Office :
- l'application ne vérifierait pas correctement la version Excel mentionnée dans un fichier. Cette vulnérabilité peut être exploitée pour provoquer une corruption de la mémoire, et éventuellement l'exécution de code arbitraire sur le système vulnérable ;
- l'application ne contrôlerait pas correctement le nombre de feuilles de travail (ou worksheets) actives, pouvant également provoquer une corruption de la mémoire ;
- l'application ne validerait pas suffisamment les informations au démarrage d'un espace de travail.
Solution
Se référer au bulletin de sécurité MS07-036 de Microsoft pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Microsoft | Office | Microsoft Excel dans la suite Microsoft Office XP Service Pack 3 ; | ||
| Microsoft | Office | Microsoft Excel dans la suite Microsoft Office 2007. | ||
| Microsoft | Office | Microsoft Excel dans la suite Microsoft Office 2000 Service Pack 3 ; | ||
| Microsoft | Office | Microsoft Excel dans la suite Microsoft Office 2003 Service Pack 2 ; |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Microsoft Excel dans la suite Microsoft Office XP Service Pack 3 ;",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Excel dans la suite Microsoft Office 2007.",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Excel dans la suite Microsoft Office 2000 Service Pack 3 ;",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
},
{
"description": "Microsoft Excel dans la suite Microsoft Office 2003 Service Pack 2 ;",
"product": {
"name": "Office",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans l\u0027application Excel de\nla suite bureautique Microsoft Office :\n\n- l\u0027application ne v\u00e9rifierait pas correctement la version Excel\n mentionn\u00e9e dans un fichier. Cette vuln\u00e9rabilit\u00e9 peut \u00eatre exploit\u00e9e\n pour provoquer une corruption de la m\u00e9moire, et \u00e9ventuellement\n l\u0027ex\u00e9cution de code arbitraire sur le syst\u00e8me vuln\u00e9rable ;\n- l\u0027application ne contr\u00f4lerait pas correctement le nombre de feuilles\n de travail (ou worksheets) actives, pouvant \u00e9galement provoquer une\n corruption de la m\u00e9moire ;\n- l\u0027application ne validerait pas suffisamment les informations au\n d\u00e9marrage d\u0027un espace de travail.\n\n## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 MS07-036 de Microsoft pour\nl\u0027obtention des correctifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2007-3029",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-3029"
},
{
"name": "CVE-2007-3030",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-3030"
},
{
"name": "CVE-2007-1756",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-1756"
}
],
"initial_release_date": "2007-07-11T00:00:00",
"last_revision_date": "2007-07-11T00:00:00",
"links": [],
"reference": "CERTA-2007-AVI-291",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-07-11T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": null,
"title": "Vuln\u00e9rabilit\u00e9s dans Microsoft Excel",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS07-036 du 10 juillet 2007",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS07-036.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.