CERTA-2009-AVI-231

Vulnerability from certfr_avis - Published: - Updated:

Deux vulnérabilités dans Google Chrome, dont une permettant l'exécution de code arbitraire à distance, ont été corrigées.

Description

Deux vulnérabilités affectant la gestion de certains événements ont été corrigées. Une personne malveillante peut les exploiter au moyen d'une page spécialement réalisée et ainsi exécuter du code arbitraire à distance ou accéder à des données personnelles.

Solution

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

Les versions de Google Chrome antérieures à 2.0.172.31.

Impacted products
Vendor Product Description

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cp\u003eLes versions de Google Chrome  ant\u00e9rieures \u00e0 2.0.172.31.\u003c/p\u003e",
  "content": "## Description\n\nDeux vuln\u00e9rabilit\u00e9s affectant la gestion de certains \u00e9v\u00e9nements ont \u00e9t\u00e9\ncorrig\u00e9es. Une personne malveillante peut les exploiter au moyen d\u0027une\npage sp\u00e9cialement r\u00e9alis\u00e9e et ainsi ex\u00e9cuter du code arbitraire \u00e0\ndistance ou acc\u00e9der \u00e0 des donn\u00e9es personnelles.\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-2009-1718",
      "url": "https://www.cve.org/CVERecord?id=CVE-2009-1718"
    },
    {
      "name": "CVE-2009-1690",
      "url": "https://www.cve.org/CVERecord?id=CVE-2009-1690"
    }
  ],
  "links": [
    {
      "title": "Bulletin de mise \u00e0 jour de Google Chrome du 9 juin 2009 :",
      "url": "http://googlechromereleases.blogspot.com/2009/06/stable-update-2-webkit-security-fixes.html"
    }
  ],
  "reference": "CERTA-2009-AVI-231",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2009-06-12T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    },
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    }
  ],
  "summary": "Deux vuln\u00e9rabilit\u00e9s dans Google Chrome, dont une permettant l\u0027ex\u00e9cution\nde code arbitraire \u00e0 distance, ont \u00e9t\u00e9 corrig\u00e9es.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans Google Chrome",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de mise \u00e0 jour Google chrome du 9 juin 2009",
      "url": null
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…