CERTA-2005-AVI-123

Vulnerability from certfr_avis - Published: 2005-03-29 - Updated: 2005-03-29

Plusieurs vulnérabilités découvertes dans les produits Norton AntiVirus de Symantec permettent à un utilisateur mal intentionné d'effectuer un déni de service à distance.

Description

L'application Norton Antivirus de Symantec présente deux vulnérabilités qui permettent à un individu malveillant d'effectuer à distance un déni de service sur le système vulnérable :

  • le module "Auto-Protect" effectue une surveillance en temps réel du système. Ce module engendre une erreur lors de l'analyse de certains fichiers, ce qui se traduit par un déni de service du système ;
  • une seconde vulnérabilité découverte dans la fonction "SmartScan" peut être exploitée afin de consommer tout ou partie des ressources CPU.

Solution

Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

None
Impacted products
Vendor Product Description
Symantec N/A Symantec Norton Antivirus 2005 ;
ESET Internet Security Symantec Norton Internet Security 2004 Professional ;
Symantec N/A Symantec Norton Antivirus 2004 ;
Symantec N/A Symantec Norton System Works 2004 Professional ;
Symantec N/A Symantec Norton System Works 2004 Premier.
ESET Internet Security Symantec Norton Internet Security 2005 ;
References

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [
    {
      "description": "Symantec Norton Antivirus 2005 ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Symantec",
          "scada": false
        }
      }
    },
    {
      "description": "Symantec Norton Internet Security 2004 Professional ;",
      "product": {
        "name": "Internet Security",
        "vendor": {
          "name": "ESET",
          "scada": false
        }
      }
    },
    {
      "description": "Symantec Norton Antivirus 2004 ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Symantec",
          "scada": false
        }
      }
    },
    {
      "description": "Symantec Norton System Works 2004 Professional ;",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Symantec",
          "scada": false
        }
      }
    },
    {
      "description": "Symantec Norton System Works 2004 Premier.",
      "product": {
        "name": "N/A",
        "vendor": {
          "name": "Symantec",
          "scada": false
        }
      }
    },
    {
      "description": "Symantec Norton Internet Security 2005 ;",
      "product": {
        "name": "Internet Security",
        "vendor": {
          "name": "ESET",
          "scada": false
        }
      }
    }
  ],
  "affected_systems_content": null,
  "content": "## Description\n\nL\u0027application Norton Antivirus de Symantec pr\u00e9sente deux vuln\u00e9rabilit\u00e9s\nqui permettent \u00e0 un individu malveillant d\u0027effectuer \u00e0 distance un d\u00e9ni\nde service sur le syst\u00e8me vuln\u00e9rable :\n\n-   le module \"Auto-Protect\" effectue une surveillance en temps r\u00e9el du\n    syst\u00e8me. Ce module engendre une erreur lors de l\u0027analyse de certains\n    fichiers, ce qui se traduit par un d\u00e9ni de service du syst\u00e8me ;\n-   une seconde vuln\u00e9rabilit\u00e9 d\u00e9couverte dans la fonction \"SmartScan\"\n    peut \u00eatre exploit\u00e9e afin de consommer tout ou partie des ressources\n    CPU.\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": [],
  "initial_release_date": "2005-03-29T00:00:00",
  "last_revision_date": "2005-03-29T00:00:00",
  "links": [],
  "reference": "CERTA-2005-AVI-123",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2005-03-29T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "D\u00e9ni de service"
    }
  ],
  "summary": "Plusieurs vuln\u00e9rabilit\u00e9s d\u00e9couvertes dans les produits Norton AntiVirus\nde Symantec permettent \u00e0 un utilisateur mal intentionn\u00e9 d\u0027effectuer un\nd\u00e9ni de service \u00e0 distance.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s de Norton AntiVirus",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Symantec SYM05-06 du 28 mars 2005",
      "url": "http://securityresponse.symantec.com/avcenter/security/Content/2005.03.28.html"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON
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.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.