CERTA-2006-AVI-191
Vulnerability from certfr_avis - Published: 2006-05-10 - Updated: 2006-05-10
Un utilisateur mal intentionné peut soumettre à l'antivirus une archive cab volontairement construite pour exécuter du code arbitraire.
Description
Une erreur dans la gestion des tampons mémoire lors de la décompression des archives cab peut être exploitée pour exécuter du code arbitraire, si la configuration prévoit l'analyse de telles archives. L'insertion en pièce jointe d'un message vers l'équipement de la victime, permet une action à distance.
Solution
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| Sophos | N/A | Sophos Anti-Virus Small Business Edition ; | ||
| Sophos | N/A | Sophos MailMonitor for Notes/Domino, SMTP ; | ||
| Sophos | N/A | Sophos Anti-Virus 3.x, 4.x et 5.x ; | ||
| Sophos | N/A | Sophos PureMessage for UNIX 4.x, 5.x ; | ||
| Sophos | N/A | Sophos PureMessage for Windows/Exchange 2.x ; | ||
| Sophos | N/A | Sophos PureMessage Small Business Edition 2.x. |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Sophos Anti-Virus Small Business Edition ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Sophos",
"scada": false
}
}
},
{
"description": "Sophos MailMonitor for Notes/Domino, SMTP ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Sophos",
"scada": false
}
}
},
{
"description": "Sophos Anti-Virus 3.x, 4.x et 5.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Sophos",
"scada": false
}
}
},
{
"description": "Sophos PureMessage for UNIX 4.x, 5.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Sophos",
"scada": false
}
}
},
{
"description": "Sophos PureMessage for Windows/Exchange 2.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "Sophos",
"scada": false
}
}
},
{
"description": "Sophos PureMessage Small Business Edition 2.x.",
"product": {
"name": "N/A",
"vendor": {
"name": "Sophos",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne erreur dans la gestion des tampons m\u00e9moire lors de la d\u00e9compression\ndes archives cab peut \u00eatre exploit\u00e9e pour ex\u00e9cuter du code arbitraire,\nsi la configuration pr\u00e9voit l\u0027analyse de telles archives. L\u0027insertion en\npi\u00e8ce jointe d\u0027un message vers l\u0027\u00e9quipement de la victime, permet une\naction \u00e0 distance.\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-2006-0994",
"url": "https://www.cve.org/CVERecord?id=CVE-2006-0994"
}
],
"initial_release_date": "2006-05-10T00:00:00",
"last_revision_date": "2006-05-10T00:00:00",
"links": [],
"reference": "CERTA-2006-AVI-191",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2006-05-10T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Un utilisateur mal intentionn\u00e9 peut soumettre \u00e0 l\u0027antivirus une archive\n\u003cspan class=\"textit\"\u003ecab\u003c/span\u003e volontairement construite pour ex\u00e9cuter\ndu code arbitraire.\n",
"title": "Vuln\u00e9rabilit\u00e9 des antivirus Sophos",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 Sophos",
"url": "http://www.sophos.com/support/knowledgebase/article/4934.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.