CERTA-2008-AVI-059
Vulnerability from certfr_avis - Published: 2008-02-07 - Updated: 2008-02-07
Plusieurs vulnérabilités ont été identifiées dans les applications Apple QuickTime et iPhoto. L'une d'elles a d'ailleurs fait l'objet de l'alerte CERTA-2008-ALE-001 publiée le 11 janvier 2008.
Les conséquences de l'exploitation de ces vulnérabilités sont variées, permettant pour certaines d'exécuter du code arbitraire à distance sur un système vulnérable.
Description
Plusieurs vulnérabilités ont été identifiées dans les applications Apple QuickTime et iPhoto.
L'une d'elles, sur QuickTime, a d'ailleurs fait l'objet de l'alerte CERTA-2008-ALE-001 publiée le 11 janvier 2008. Elle concerne un dépassement de mémoire tampon lors d'une tentative infructueuse de lecture de lecture d'un fichier via le protocole Real Time Streaming Protocol (RTSP).
iPhoto, quant à lui, ne manipulerait pas correctement certaines diffusions de photos (photocast) spécialement construites.
Solution
Se référer aux bulletins 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": "les versions d\u0027Apple iPhoto ant\u00e9rieures \u00e0 7.1.2.",
"product": {
"name": "N/A",
"vendor": {
"name": "Apple",
"scada": false
}
}
},
{
"description": "Les versions d\u0027Apple QuickTime ant\u00e9rieures \u00e0 7.4.1 ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Apple",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nPlusieurs vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans les applications Apple\nQuickTime et iPhoto.\n\nL\u0027une d\u0027elles, sur QuickTime, a d\u0027ailleurs fait l\u0027objet de l\u0027alerte\nCERTA-2008-ALE-001 publi\u00e9e le 11 janvier 2008. Elle concerne un\nd\u00e9passement de m\u00e9moire tampon lors d\u0027une tentative infructueuse de\nlecture de lecture d\u0027un fichier via le protocole Real Time Streaming\nProtocol (RTSP).\n\niPhoto, quant \u00e0 lui, ne manipulerait pas correctement certaines\ndiffusions de photos (photocast) sp\u00e9cialement construites.\n\n## Solution\n\nSe r\u00e9f\u00e9rer aux bulletins de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2008-0234",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-0234"
},
{
"name": "CVE-2008-0043",
"url": "https://www.cve.org/CVERecord?id=CVE-2008-0043"
}
],
"initial_release_date": "2008-02-07T00:00:00",
"last_revision_date": "2008-02-07T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 Apple 307407 du 04 f\u00e9vrier 2008 :",
"url": "http://docs.info.apple.com/article.html?artnum=307407"
},
{
"title": "Bulletin de s\u00e9curit\u00e9 Apple 307398 du 04 f\u00e9vrier 2008 :",
"url": "http://docs.info.apple.com/article.html?artnum=307398"
},
{
"title": "Document du CERTA CERTA-2008-ALE-001 du 14 janvier 2008 :",
"url": "http://www.certa.ssi.gouv.fr/site/CERTA-2008-ALE-001/index.html"
}
],
"reference": "CERTA-2008-AVI-059",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2008-02-07T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "Plusieurs vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 identifi\u00e9es dans les applications Apple\nQuickTime et iPhoto. L\u0027une d\u0027elles a d\u0027ailleurs fait l\u0027objet de l\u0027alerte\nCERTA-2008-ALE-001 publi\u00e9e le 11 janvier 2008.\n\nLes cons\u00e9quences de l\u0027exploitation de ces vuln\u00e9rabilit\u00e9s sont vari\u00e9es,\npermettant pour certaines d\u0027ex\u00e9cuter du code arbitraire \u00e0 distance sur\nun syst\u00e8me vuln\u00e9rable.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans Apple QuickTime et iPhoto",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletins de s\u00e9curit\u00e9 Apple 307407 et 307398 du 04 f\u00e9vrier 2008",
"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.