CERTA-2010-AVI-337

Vulnerability from certfr_avis - Published: 2010-07-27 - Updated: 2010-07-27

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

Description

Plusieurs failles ont été corrigées dans le navigateur Google Chrome. Leur exploitation peut permettre notamment l'exécution de code arbitraire à distance. Deux contournements pour prévenir l'exploitation d'une faille concernant le noyau de Windows et une vulnérabilité de glibc ont également été implémentés dans la dernière mise à jour du 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 à 5.0.375.125.

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 5.0.375.125.\u003c/P\u003e",
  "content": "## Description\n\nPlusieurs failles ont \u00e9t\u00e9 corrig\u00e9es dans le navigateur Google Chrome.\nLeur exploitation peut permettre notamment l\u0027ex\u00e9cution de code\narbitraire \u00e0 distance. Deux contournements pour pr\u00e9venir l\u0027exploitation\nd\u0027une faille concernant le noyau de Windows et une vuln\u00e9rabilit\u00e9 de\nglibc ont \u00e9galement \u00e9t\u00e9 impl\u00e9ment\u00e9s dans la derni\u00e8re mise \u00e0 jour du\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-07-27T00:00:00",
  "last_revision_date": "2010-07-27T00:00:00",
  "links": [
    {
      "title": "Mise \u00e0 jour 5.0.375.125 de Google Chrome du 26 juillet 2010    :",
      "url": "http://googlechromereleases.blogspot.com/2010/07/stable-channel-update_26.html"
    }
  ],
  "reference": "CERTA-2010-AVI-337",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2010-07-27T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
    },
    {
      "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": "Vuln\u00e9rabilit\u00e9s dans Google Chrome",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Notes de mise \u00e0 jour 5.0.375.125 de Google Chrome du 26 juillet 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…