CERTA-2010-AVI-578

Vulnerability from certfr_avis - Published: 2010-12-06 - Updated: 2010-12-06

De multiples vulnérabilités ont été corrigées dans Google Chrome.

Description

De multiples vulnérabilités dans Google Chrome  ont été découvertes. Google annonce que plus de 800 corrections ont été apportées dans cette nouvelle version de Chrome. A noter, Google indique que cette nouvelle version de Chrome intégre désormais un lecteur PDF faisant usage des fonctions de sécurité de type "bac à sable" Sandbox présentes dans le navigateur.

Solution

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

Google Chrome versions antérieures à 8.0.552.215.

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\u003eGoogle Chrome versions ant\u00e9rieures \u00e0  8.0.552.215.\u003c/p\u003e",
  "content": "## Description\n\nDe multiples vuln\u00e9rabilit\u00e9s dans Google Chrome\u00a0 ont \u00e9t\u00e9 d\u00e9couvertes.\nGoogle annonce que plus de 800 corrections ont \u00e9t\u00e9 apport\u00e9es dans cette\nnouvelle version de Chrome. A noter, Google indique que cette nouvelle\nversion de Chrome int\u00e9gre d\u00e9sormais un lecteur PDF faisant usage des\nfonctions de s\u00e9curit\u00e9 de type \"bac \u00e0 sable\" Sandbox pr\u00e9sentes dans le\nnavigateur.\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": "2010-12-06T00:00:00",
  "last_revision_date": "2010-12-06T00:00:00",
  "links": [
    {
      "title": "Note de version Google Chrome    2010/12/stable-beta-channel-updates.html du 02 d\u00e9cembre 2010 :",
      "url": "http://googlechromereleases.blogspot.com/2010/12/stable-beta-channel-updates.html"
    }
  ],
  "reference": "CERTA-2010-AVI-578",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2010-12-06T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    },
    {
      "description": "D\u00e9ni de service"
    },
    {
      "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
    }
  ],
  "summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans Google Chrome.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans Google Chrome",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Note de mise \u00e0 jour 8.0.552.215 de Google Chrome du 2 d\u00e9cembre 2010",
      "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…