-
Notifications
You must be signed in to change notification settings - Fork 16k
fix: prevent UAF crash in setCertificateVerifyProc #33204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
patches/chromium/network_service_allow_remote_certificate_verification_logic.patch
Outdated
Show resolved
Hide resolved
Compilation errors needs to be addressed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like tests are legitimately failing.
Release Notes Persisted
|
I was unable to backport this PR to "16-x-y" cleanly; |
I was unable to backport this PR to "15-x-y" cleanly; |
I was unable to backport this PR to "17-x-y" cleanly; |
I have automatically backported this PR to "18-x-y", please check out #33253 |
@nornagon do you have any idea when we could expect this fix to land in a 17+.x.y stable release? |
Description of Change
This fixes a bug with the RemoteCertVerifier patch that drives the
ses.setCertificateVerifyProc
API. When an in-flight request was cancelledafter the procedure was invoked but before the result was received, a
use-after-free could occur.
Fixes #31675.
Checklist
npm test
passesRelease Notes
Notes: Fixed a network service crash that could occur when using setCertificateVerifyProc.