CERTA-2007-AVI-370
Vulnerability from certfr_avis - Published: 2007-08-21 - Updated: 2007-08-21
Deux vulnérabilités dans les produits ZoneLabs permettent une élévation de privilèges.
Description
Deux vulnérabilités ont été découvertes dans les produits ZoneLabs.
Lorsqu'un administrateur installe un produit ZoneLabs de la famille ZoneAlarm, un paramétrage par défaut permet à tout utilisateur de modifier les fichiers installés (référence CVE-2005-2932). Certains de ces fichiers sont exécutés avec les droits system.
Une vulnérabilité a été découverte dans le pilote vsdatant.sys. Cette vulnérabilité permet à un utilisateur local de modifier directement le contenu de certaines zones de la mémoire (référence CVE-2007-4216).
Solution
Mettre à jour en version 7.0.362 (cf. section Documentation).
None| Vendor | Product | Description | ||
|---|---|---|---|---|
| ESET | Security | ZoneAlarm Security Suite versions 5.x ; | ||
| ESET | N/A | ZoneAlarm Antivirus versions 5.x, 6.x ; | ||
| N/A | N/A | ZoneAlarm versions 2.x, 3.x, 4.x, 5.x, 6.x, 7.x ; | ||
| N/A | N/A | ZoneAlarm Plus versions 3.x, 4.x ; | ||
| ESET | Internet Security | ZoneAlarm Internet Security Suite versions 6.x ; | ||
| ESET | Security | ZoneAlarm Wireless Security versions 5.x. | ||
| ESET | N/A | ZoneAlarm Pro versions 2.x, 3.x, 4.x, 5.x, 6.x ; | ||
| ESET | N/A | ZoneAlarm Anti-Spyware versions 6.x ; |
| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "ZoneAlarm Security Suite versions 5.x ;",
"product": {
"name": "Security",
"vendor": {
"name": "ESET",
"scada": false
}
}
},
{
"description": "ZoneAlarm Antivirus versions 5.x, 6.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "ESET",
"scada": false
}
}
},
{
"description": "ZoneAlarm versions 2.x, 3.x, 4.x, 5.x, 6.x, 7.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
},
{
"description": "ZoneAlarm Plus versions 3.x, 4.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "N/A",
"scada": false
}
}
},
{
"description": "ZoneAlarm Internet Security Suite versions 6.x ;",
"product": {
"name": "Internet Security",
"vendor": {
"name": "ESET",
"scada": false
}
}
},
{
"description": "ZoneAlarm Wireless Security versions 5.x.",
"product": {
"name": "Security",
"vendor": {
"name": "ESET",
"scada": false
}
}
},
{
"description": "ZoneAlarm Pro versions 2.x, 3.x, 4.x, 5.x, 6.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "ESET",
"scada": false
}
}
},
{
"description": "ZoneAlarm Anti-Spyware versions 6.x ;",
"product": {
"name": "N/A",
"vendor": {
"name": "ESET",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans les produits ZoneLabs.\n\nLorsqu\u0027un administrateur installe un produit ZoneLabs de la famille\nZoneAlarm, un param\u00e9trage par d\u00e9faut permet \u00e0 tout utilisateur de\nmodifier les fichiers install\u00e9s (r\u00e9f\u00e9rence CVE-2005-2932). Certains de\nces fichiers sont ex\u00e9cut\u00e9s avec les droits system.\n\nUne vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 d\u00e9couverte dans le pilote vsdatant.sys. Cette\nvuln\u00e9rabilit\u00e9 permet \u00e0 un utilisateur local de modifier directement le\ncontenu de certaines zones de la m\u00e9moire (r\u00e9f\u00e9rence CVE-2007-4216).\n\n## Solution\n\nMettre \u00e0 jour en version 7.0.362 (cf. section Documentation).\n",
"cves": [
{
"name": "CVE-2005-2932",
"url": "https://www.cve.org/CVERecord?id=CVE-2005-2932"
},
{
"name": "CVE-2007-4216",
"url": "https://www.cve.org/CVERecord?id=CVE-2007-4216"
}
],
"initial_release_date": "2007-08-21T00:00:00",
"last_revision_date": "2007-08-21T00:00:00",
"links": [
{
"title": "Page de mise \u00e0 jour de ZoneAlarm :",
"url": "http://www.zonealarm.com/store/content/support/zasc/cfu.jsp?dc=12bms\u0026ctry=FR\u0026lang=fr\u0026lid=db_updates"
}
],
"reference": "CERTA-2007-AVI-370",
"revisions": [
{
"description": "version initiale.",
"revision_date": "2007-08-21T00:00:00.000000"
}
],
"risks": [
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": "Deux vuln\u00e9rabilit\u00e9s dans les produits \u003cspan\nclass=\"textit\"\u003eZoneLabs\u003c/span\u003e permettent une \u00e9l\u00e9vation de privil\u00e8ges.\n",
"title": "Vuln\u00e9rabilit\u00e9s dans les produits ZoneLabs",
"vendor_advisories": [
{
"published_at": null,
"title": "Bulletins de s\u00e9curit\u00e9 iDefense du 20 ao\u00fbt 2007",
"url": "http://labs.idefense.com/intelligence/vulnerabilities/display.php?id=585"
}
]
}
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.