CERTFR-2016-AVI-180

Vulnerability from certfr_avis - Published: - Updated:

De multiples vulnérabilités ont été corrigées dans Google Chrome. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

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 à 51.0.2704.63 pour Windows, Mac et Linux

Impacted products
Vendor Product Description
References

Show details on source website
To clipboard 

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cP\u003eGoogle Chrome versions ant\u00e9rieures \u00e0 51.0.2704.63 pour  Windows, Mac et Linux\u003c/P\u003e",
  "content": "## 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-2016-1681",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1681"
    },
    {
      "name": "CVE-2016-1689",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1689"
    },
    {
      "name": "CVE-2016-1691",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1691"
    },
    {
      "name": "CVE-2016-1695",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1695"
    },
    {
      "name": "CVE-2016-1679",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1679"
    },
    {
      "name": "CVE-2016-1674",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1674"
    },
    {
      "name": "CVE-2016-1686",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1686"
    },
    {
      "name": "CVE-2016-1673",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1673"
    },
    {
      "name": "CVE-2016-1684",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1684"
    },
    {
      "name": "CVE-2016-1692",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1692"
    },
    {
      "name": "CVE-2016-1682",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1682"
    },
    {
      "name": "CVE-2016-1676",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1676"
    },
    {
      "name": "CVE-2016-1694",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1694"
    },
    {
      "name": "CVE-2016-1672",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1672"
    },
    {
      "name": "CVE-2016-1685",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1685"
    },
    {
      "name": "CVE-2016-1677",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1677"
    },
    {
      "name": "CVE-2016-1693",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1693"
    },
    {
      "name": "CVE-2016-1687",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1687"
    },
    {
      "name": "CVE-2016-1690",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1690"
    },
    {
      "name": "CVE-2016-1688",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1688"
    },
    {
      "name": "CVE-2016-1678",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1678"
    },
    {
      "name": "CVE-2016-1680",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1680"
    },
    {
      "name": "CVE-2016-1675",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1675"
    },
    {
      "name": "CVE-2016-1683",
      "url": "https://www.cve.org/CVERecord?id=CVE-2016-1683"
    }
  ],
  "links": [],
  "reference": "CERTFR-2016-AVI-180",
  "revisions": [
    {
      "description": "version initiale.",
      "revision_date": "2016-05-26T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
    }
  ],
  "summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 corrig\u00e9es dans \u003cspan\nclass=\"textit\"\u003eGoogle Chrome\u003c/span\u003e. Elles permettent \u00e0 un attaquant de\nprovoquer un probl\u00e8me de s\u00e9curit\u00e9 non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur.\n",
  "title": "Multiples vuln\u00e9rabilit\u00e9s dans Google Chrome",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 Google du 25 mai 2016",
      "url": "http://googlechromereleases.blogspot.fr/2016/05/stable-channel-update_25.html?utm_source=feedburner\u0026utm_medium=feed\u0026utm_campaign=Feed:+GoogleChromeReleases+%28Google+Chrome+Releases%29"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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

Loading timeline…




    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.