CERTA-2005-AVI-501
Vulnerability from certfr_avis - Published: 2005-12-22 - Updated: 2005-12-22None
Description
Une vulnérabilité a été découverte dans un contrôle ActiveX de la bibliothèque MCINSCTL.DLL (versions 4.0.0.83 et antérieures). Un utilisateur mal intentionné peut exploiter cette vulnérabilité pour créer ou modifier des fichiers, notamment dans le répertoire de démarrage.
Solution
McAfee corrige automatiquement cette vulnérabilité par une mise à jour.
Note : Certains codes malveillants modifient
le fichier \%windir\%/system32/drivers/etc/hosts pour empêcher les
mises à jour automatiques des antivirus. Il est donc conseillé de
vérifier que cette mise à jour a bien été effectuée.
| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "McAfee VirusScan 9.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "McAfee",
"scada": false
}
}
},
{
"description": "McAfee VirusScan Professional 7.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "McAfee",
"scada": false
}
}
},
{
"description": "McAfee Security Center 6.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "McAfee",
"scada": false
}
}
},
{
"description": "McAfee VirusScan 4.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "McAfee",
"scada": false
}
}
},
{
"description": "McAfee VirusScan 8.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "McAfee",
"scada": false
}
}
},
{
"description": "McAfee VirusScan Professional 8.x.",
"product": {
"name": "N/A",
"vendor": {
"name": "McAfee",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nUne vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 d\u00e9couverte dans un contr\u00f4le ActiveX de la\nbiblioth\u00e8que MCINSCTL.DLL (versions 4.0.0.83 et ant\u00e9rieures). Un\nutilisateur mal intentionn\u00e9 peut exploiter cette vuln\u00e9rabilit\u00e9 pour\ncr\u00e9er ou modifier des fichiers, notamment dans le r\u00e9pertoire de\nd\u00e9marrage.\n\n## Solution\n\nMcAfee corrige automatiquement cette vuln\u00e9rabilit\u00e9 par une mise \u00e0 jour.\n\n\u003cspan class=\"textbf\"\u003eNote :\u003c/span\u003e Certains codes malveillants modifient\nle fichier `\\%windir\\%/system32/drivers/etc/hosts` pour emp\u00eacher les\nmises \u00e0 jour automatiques des antivirus. Il est donc conseill\u00e9 de\nv\u00e9rifier que cette mise \u00e0 jour a bien \u00e9t\u00e9 effectu\u00e9e.\n",
"cves": [
{
"name": "CVE-2005-3657",
"url": "https://www.cve.org/CVERecord?id=CVE-2005-3657"
}
],
"initial_release_date": "2005-12-22T00:00:00",
"last_revision_date": "2005-12-22T00:00:00",
"links": [
{
"title": "Bulletin de s\u00e9curit\u00e9 iDefense 12.20.05 :",
"url": "http://www.idefense.com/intelligence/vulnerabilities/display.php?id=358"
}
],
"reference": "CERTA-2005-AVI-501",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2005-12-22T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": null,
"title": "Vuln\u00e9rabilit\u00e9 dans McAfee Security Center",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletin de s\u00e9curit\u00e9 12.20.05 de iDefense",
"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.