🚨 [security] Update electron 16.0.7 → 38.0.0 (major) - #14
Open
depfu[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ electron (16.0.7 → 38.0.0) · Repo
Security Advisories 🚨
🚨 Electron has ASAR Integrity Bypass via resource modification
🚨 Electron has ASAR Integrity Bypass via resource modification
🚨 Electron has ASAR Integrity Bypass via resource modification
🚨 Electron has ASAR Integrity Bypass via resource modification
🚨 electron ASAR Integrity bypass by just modifying the content
🚨 Electron vulnerable to Heap Buffer Overflow in NativeImage
🚨 Electron vulnerable to Heap Buffer Overflow in NativeImage
🚨 Electron vulnerable to Heap Buffer Overflow in NativeImage
🚨 electron ASAR Integrity bypass by just modifying the content
🚨 ASAR Integrity bypass via filetype confusion in electron
🚨 ASAR Integrity bypass via filetype confusion in electron
🚨 ASAR Integrity bypass via filetype confusion in electron
🚨 ASAR Integrity bypass via filetype confusion in electron
🚨 ASAR Integrity bypass via filetype confusion in electron
🚨 Electron affected by libvpx's heap buffer overflow in vp8 encoding
🚨 Electron affected by libvpx's heap buffer overflow in vp8 encoding
🚨 Electron affected by libvpx's heap buffer overflow in vp8 encoding
🚨 Electron affected by libvpx's heap buffer overflow in vp8 encoding
🚨 libwebp: OOB write in BuildHuffmanTable
🚨 libwebp: OOB write in BuildHuffmanTable
🚨 libwebp: OOB write in BuildHuffmanTable
🚨 libwebp: OOB write in BuildHuffmanTable
🚨 Electron's Content-Secrity-Policy disabling eval not applied consistently in renderers with sandbox disabled
🚨 Electron context isolation bypass via nested unserializable return value
🚨 Electron context isolation bypass via nested unserializable return value
🚨 Electron context isolation bypass via nested unserializable return value
🚨 Electron vulnerable to out-of-package code execution when launched with arbitrary cwd
🚨 Electron vulnerable to out-of-package code execution when launched with arbitrary cwd
🚨 Electron vulnerable to out-of-package code execution when launched with arbitrary cwd
🚨 Electron vulnerable to out-of-package code execution when launched with arbitrary cwd
🚨 Electron vulnerable to out-of-package code execution when launched with arbitrary cwd
🚨 Electron context isolation bypass via nested unserializable return value
🚨 Electron's Content-Secrity-Policy disabling eval not applied consistently in renderers with sandbox disabled
🚨 Heap buffer overflow in GPU
🚨 Exfiltration of hashed SMB credentials on Windows via file:// redirect
🚨 Exfiltration of hashed SMB credentials on Windows via file:// redirect
🚨 Exfiltration of hashed SMB credentials on Windows via file:// redirect
🚨 Compromised child renderer processes could obtain IPC access without nodeIntegrationInSubFrames being enabled
🚨 Compromised child renderer processes could obtain IPC access without nodeIntegrationInSubFrames being enabled
🚨 Compromised child renderer processes could obtain IPC access without nodeIntegrationInSubFrames being enabled
🚨 AutoUpdater module fails to validate certain nested components of the bundle
🚨 AutoUpdater module fails to validate certain nested components of the bundle
🚨 AutoUpdater module fails to validate certain nested components of the bundle
🚨 Renderers can obtain access to random bluetooth device without permission in Electron
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
🆕 @types/cacheable-request (added, 6.0.3)
🆕 @types/http-cache-semantics (added, 4.0.4)
🆕 @types/keyv (added, 3.1.4)
🆕 @types/responselike (added, 1.0.3)
🆕 @types/yauzl (added, 2.10.3)
🆕 cacheable-lookup (added, 5.0.4)
🆕 http2-wrapper (added, 1.0.3)
🆕 quick-lru (added, 5.1.1)
🆕 resolve-alpn (added, 1.2.1)
🆕 undici-types (added, 6.21.0)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands