CERTFR-2021-AVI-048
Vulnerability from certfr_avis - Published: 2021-01-20 - Updated: 2021-01-20
De multiples vulnérabilités ont été découvertes 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).
None| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Google Chrome versions ant\u00e9rieures \u00e0 88.0.4324.96",
"product": {
"name": "Chrome",
"vendor": {
"name": "Google",
"scada": false
}
}
}
],
"affected_systems_content": null,
"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-2021-21133",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21133"
},
{
"name": "CVE-2021-21136",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21136"
},
{
"name": "CVE-2021-21138",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21138"
},
{
"name": "CVE-2021-21128",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21128"
},
{
"name": "CVE-2021-21139",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21139"
},
{
"name": "CVE-2021-21140",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21140"
},
{
"name": "CVE-2021-21132",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21132"
},
{
"name": "CVE-2021-21126",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21126"
},
{
"name": "CVE-2021-21135",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21135"
},
{
"name": "CVE-2021-21129",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21129"
},
{
"name": "CVE-2021-21131",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21131"
},
{
"name": "CVE-2021-21122",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21122"
},
{
"name": "CVE-2021-21141",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21141"
},
{
"name": "CVE-2021-21124",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21124"
},
{
"name": "CVE-2021-21117",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21117"
},
{
"name": "CVE-2021-21123",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21123"
},
{
"name": "CVE-2021-21120",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21120"
},
{
"name": "CVE-2020-16044",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-16044"
},
{
"name": "CVE-2021-21137",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21137"
},
{
"name": "CVE-2021-21121",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21121"
},
{
"name": "CVE-2021-21130",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21130"
},
{
"name": "CVE-2021-21127",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21127"
},
{
"name": "CVE-2021-21118",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21118"
},
{
"name": "CVE-2021-21119",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21119"
},
{
"name": "CVE-2021-21134",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21134"
},
{
"name": "CVE-2021-21125",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-21125"
}
],
"initial_release_date": "2021-01-20T00:00:00",
"last_revision_date": "2021-01-20T00:00:00",
"links": [],
"reference": "CERTFR-2021-AVI-048",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2021-01-20T00:00:00.000000"
}
],
"risks": [
{
"description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans Google Chrome.\nElles permettent \u00e0 un attaquant de provoquer un probl\u00e8me de s\u00e9curit\u00e9 non\nsp\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 19 janvier 2021",
"url": "https://chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop_19.html"
}
]
}
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.
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
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.