nday
CVE-2023-5217

Google Chromium libvpx Heap Buffer Overflow Vulnerability

Google / Chromium libvpx, Chrome, libvpx

Se incluyó en el KEV 4 días después de la divulgación. nday aún no tiene constancia de una corrección; eso no significa que no exista parche. Ninguna de las cuatro fuentes de PoC la recoge.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

buffer overflow / out-of-bounds write
CWE-787, stated by the ADP CISA-ADP, NVD's analysts y NVD, republishing 134c704f-9b21-4f2e-91b3-4a467353bcc0
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the ADP CISA-ADP
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the ADP CISA-ADP
iOS / iPadOS
CPE names NVD's analysts give as vulnerable: o:apple:ipados, o:apple:iphone_os
Chrome
affected products in the CVE record: Google · ChromeCPE names NVD's analysts give as vulnerable: a:google:chrome
Firefox
CPE names NVD's analysts give as vulnerable: a:mozilla:firefox
Microsoft Edge
CPE names NVD's analysts give as vulnerable: a:microsoft:edge, a:microsoft:edge_chromium
Thunderbird
CPE names NVD's analysts give as vulnerable: a:mozilla:thunderbird
operating system
CPE names NVD's analysts give as vulnerable: o:apple:ipados, o:apple:iphone_osthe product type of iOS / iPadOS in nday's product registry
browser
affected products in the CVE record: Google · ChromeCPE names NVD's analysts give as vulnerable: a:google:chrome, a:microsoft:edge, a:microsoft:edge_chromium, a:mozilla:firefoxthe product type of Chrome, Microsoft Edge y Firefox in nday's product registry
mail / collaboration
CPE names NVD's analysts give as vulnerable: a:mozilla:thunderbirdthe product type of Thunderbird in nday's product registry
etapa
KEV
divulgación
divulgación → KEV
T+4d KEV: solo fecha
cvss
8.8 HIGH v3.1
fecha límite KEV
2023-10-23

Ciclo de vida

Eje x en UTC; punto = minuto exacto, barra ancha = solo fecha, hueco = desconocida o inferida.
fecha desconocida
DISdivulgada
2023-09-28T15:23Z
PATparcheada
sin registro aún
ANAanalizada
sin registro aún
POCPoC
sin registro aún
ITWexplotada
≤ 2023-10-02, inferida de KEV
KEVen KEV
2023-10-02, solo fecha

Descripción

Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to 117.0.5938.132 and libvpx 1.13.1 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:R
Required: a user must do something, such as open a file or click a link

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, added by the ADP CISA-ADP.

Registro de eventos

+DISdivulgación

Chrome publicó el registro CVE. CVSS 8.8, severidad alta. La evaluación SSVC de CISA asigna a la explotación el valor active.

fuente cvelist · nday , importación masiva · en bruto
{
  "id": 17374,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2023-5217",
  "occurred_at": "2023-09-28T15:23:18.34Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-5217",
      "date_added": "2023-10-02"
    },
    "cvss": {
      "source": "adp:CISA-ADP",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 8.8,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2023-11-15T16:38:17.360361Z",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2023-09-28T15:23:18.340Z",
    "assigner_short_name": "Chrome"
  }
}
2023-10-02solo fecha, según la fuente
+KEVinclusión en KEV

CISA la incluyó en su catálogo de vulnerabilidades explotadas conocidas (KEV) y fijó el 2023-10-23 como fecha límite de corrección. Uso en campañas de ransomware: desconocido.

fuente kev · nday , importación masiva · en bruto
{
  "id": 773,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2023-10-02T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-787"
    ],
    "notes": "https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_27.html; https://nvd.nist.gov/vuln/detail/CVE-2023-5217",
    "product": "Chromium libvpx",
    "due_date": "2023-10-23",
    "precision": "day",
    "date_added": "2023-10-02",
    "vendor_project": "Google",
    "forensic_triage": "No",
    "required_action": "Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.",
    "vulnerability_name": "Google Chromium libvpx Heap Buffer Overflow Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2023-10-02inferido, sin fuente directa
~ITWexplotación activa

Ninguna fuente indica cuándo empezó la explotación. La inclusión en el KEV implica que ya se estaba produciendo, así que solo se conoce un límite superior. La evaluación SSVC de CISA asigna a la explotación el valor active.

fundamento: kev y evaluación de CISA en cvelist

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Debate de investigadores

0 investigadores lo mencionaron en los últimos 7 días

Publicaciones en X de investigadores de la lista de nday que mencionan este CVE, tal como se publicaron. nday no las verifica.

nday aún no ha recopilado publicaciones en X de investigadores de su lista sobre este CVE.

Discussion

0 comments

No comments yet.