Skip to content
NewA calmer, faster ZeroHour
Exploit / PoCcriticalExploited in the wild

Yet another Chrome zero-day exploited in the wild! (CVE-2023-5217)

Help Net Securityby @helpnetsecurity ()2 min read3 · 1 read
Analyze CVE-2023-5217 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2023-41061
Actively Exploited Wallet Flaw Enables Code Execution on Apple iOS, iPadOS, watchOS
7.84%KEV
KEV
CVE-2023-41064
ImageIO Buffer Overflow in Apple iOS, iPadOS, and macOS Allows Code Execution
7.853%KEV
KEV
CVE-2023-44488
VP9 in libvpx before 1.13.1 mishandles widths, leading to a crash related to encoding
7.52%
CVE-2023-4863
Out-of-Bounds Write in Google Chromium WebP Image Codec Actively Exploited
8.8100%KEVPoC ×4
KEV
CVE-2023-5129
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority
——
CVE-2023-5186
+1 related CVE
Use after free in Passwords in Google Chrome prior to 117.0.5938.132 allowed a remote attacker who convinced a user to engage in specific UI interaction to…
8.8<1%
CVE-2023-5217
Heap Buffer Overflow in Google Chromium libvpx (CVE-2023-5217) Added to CISA KEV
8.849%KEVPoC
KEV

From the original article

2 min read at helpnetsecurity.com

Google has fixed another critical zero-day vulnerability (CVE-2023-5217) in Chrome that is being exploited in the wild. The vulnerability is caused by a heap buffer overflow in vp8 encoding in libvpx – a video codec library from Google and the Alliance for Open Media (AOMedia). CVE-2023-5217 has been fixed in Google Chrome 117.

Help Net Security

By @helpnetsecurity · helpnetsecurity.com

Read the full article at Help Net Security

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.