CERTA-2007-AVI-080
Vulnerability from certfr_avis - Published: 2007-02-14 - Updated: 2007-02-14None
Description
Une vulnérabilité, de type débordement de mémoire tampon, a été identifiée dans le service d'Acquisition d'Image Windows (WIA) (ou Windows Image Acquisition) de Microsoft Windows. Ce service démarre manuellement. Il sert d'interface entre les applications logicielles (Adobe Photoshop par exemple) et les matériels multimédia, tels que les appareils photo numériques, les scanners, ou les webcams.
Une personne malveillante, disposant d'une session sur la machine vulnérable, peut lancer une application exploitant cette vulnérabilité, afin d'élever ses privilèges à ceux de l'administrateur. Il serait également possible d'exploiter cette vulnérabilité par le biais d'un Cheval de Troie.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Microsoft Windows XP SP 2.",
"product": {
"name": "Windows",
"vendor": {
"name": "Microsoft",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9, de type d\u00e9bordement de m\u00e9moire tampon, a \u00e9t\u00e9\nidentifi\u00e9e dans le service d\u0027Acquisition d\u0027Image Windows (WIA) (ou\nWindows Image Acquisition) de Microsoft Windows. Ce service d\u00e9marre\nmanuellement. Il sert d\u0027interface entre les applications logicielles\n(Adobe Photoshop par exemple) et les mat\u00e9riels multim\u00e9dia, tels que les\nappareils photo num\u00e9riques, les scanners, ou les webcams.\n\nUne personne malveillante, disposant d\u0027une session sur la machine\nvuln\u00e9rable, peut lancer une application exploitant cette vuln\u00e9rabilit\u00e9,\nafin d\u0027\u00e9lever ses privil\u00e8ges \u00e0 ceux de l\u0027administrateur. Il serait\n\u00e9galement possible d\u0027exploiter cette vuln\u00e9rabilit\u00e9 par le biais d\u0027un\nCheval de Troie.\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-2007-0210",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-0210"
}
],
"initial_release_date": "2007-02-14T00:00:00",
"last_revision_date": "2007-02-14T00:00:00",
"links": [],
"reference": "CERTA-2007-AVI-080",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-02-14T00:00:00.000000"
}
],
"risks": [
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": null,
"title": "Vuln\u00e9rabilit\u00e9 de l\u0027Acquisition d\u0027Image Windows (WIA)",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Microsoft MS07-007 du 13 f\u00e9vrier 2007",
"url": "http://www.microsoft.com/technet/security/Bulletin/MS07-007.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.