Status Update
Comments
kr...@google.com <kr...@google.com> #2
zh...@gmail.com <zh...@gmail.com> #3
Simpler Reproduction Case:
- Open chrome://download-internals/ and close it
- Open new tab with chrome://download-internals/, input any valid URL and click Download button
pe...@google.com <pe...@google.com> #4
ar...@chromium.org <ar...@chromium.org> #5
[Secondary security shepherd]
@rohitrao: Did you make any progress? +CC: xingliu@ who authored the patch causing the issue. You might want to help?
pe...@google.com <pe...@google.com> #6
If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?
If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.
Thanks for your time! To disable nags, add Disable-Nags (case sensitive) to the Chromium Labels custom field.
ro...@google.com <ro...@google.com>
ap...@google.com <ap...@google.com> #7
Branch: main
commit 952757624c6c06c443c487771d070b52719d17b0
Author: Rohit Rao <rohitrao@chromium.org>
Date: Fri Mar 15 16:42:14 2024
[ios] Call RemoveObserver when destroying DownloadInternalsUIMessageHandler.
Bug: 326607008
Change-Id: Ifb091ed4917c253ea7d2122d9dfdc94734b1e75e
Reviewed-on:
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1273470}
M ios/chrome/browser/webui/ui_bundled/download_internals_ui.cc
ro...@google.com <ro...@google.com>
pe...@google.com <pe...@google.com> #8
Requesting merge to stable (M123) because latest trunk commit (1273470) appears to be after stable branch point (1262506).
Thank you for fixing this security bug! We aim to ship security fixes as quickly as possible, to limit their opportunity for exploitation as an "n-day" (that is, a bug where git fixes are developed into attacks before those fixes reach users).
We have determined this fix is necessary on milestone(s): [].
Please answer the following questions so that we can safely process this merge request:
1. Which CLs should be backmerged? (Please include Gerrit links.)
2. Has this fix been verified on Canary to not pose any stability regressions?
3. Does this fix pose any potential non-verifiable stability risks?
4. Does this fix pose any known compatibility risks?
5. Does it require manual verification by the test team? If so, please describe required testing.
pe...@google.com <pe...@google.com> #9
Please answer the following questions so that we can safely process your merge request:
1. Why does your merge fit within the merge criteria for these milestones?
- Chrome Browser:
- Chrome OS:
2. What changes specifically would you like to merge? Please link to Gerrit.
3. Have the changes been released and tested on canary?
4. Is this a new feature? If yes, is it behind a Finch flag and are experiments active in any release channels?
5. [Chrome OS only]: Was the change reviewed and approved by the Eng Prod Representative?
6. If this merge addresses a major issue in the stable channel, does it require manual verification by the test team? If so, please describe required testing.
Please contact the milestone owner if you have questions.
Owners: govind (Android), govind (iOS), dgagnon (ChromeOS), srinivassista (Desktop)
pe...@google.com <pe...@google.com> #10
Please answer the following questions so that we can safely process your merge request:
1. Why does your merge fit within the merge criteria for these milestones?
- Chrome Browser:
- Chrome OS:
2. What changes specifically would you like to merge? Please link to Gerrit.
3. Have the changes been released and tested on canary?
4. Is this a new feature? If yes, is it behind a Finch flag and are experiments active in any release channels?
5. [Chrome OS only]: Was the change reviewed and approved by the Eng Prod Representative?
6. If this merge addresses a major issue in the stable channel, does it require manual verification by the test team? If so, please describe required testing.
Please contact the milestone owner if you have questions.
Owners: eakpobaro (Android), eakpobaro (iOS), ceb (ChromeOS), pbommana (Desktop)
am...@chromium.org <am...@chromium.org> #11
Since we don't have comparable Canary data for iOS as we do on other platforms, I can't review Canary data for this fix. (
Please merge this fix to M123 Stable / branch 6312 and M122 Extended / branch 6261 at your earliest convenience and before EOD Thursday, 21 March so this fix can be included in the next respective security updates -- thank you!
am...@google.com <am...@google.com> #12
Please do NOT publicly disclose details until a fix has been released to all our users. Early public disclosure may cancel the provisional reward. Also, please be considerate about disclosure when the bug affects a core library that may be used by other products. Please do NOT share this information with third parties who are not directly involved in fixing the bug. Doing so may cancel the provisional reward. Please be honest if you have already disclosed anything publicly or to third parties. Lastly, we understand that some of you are not interested in money. We offer the option to donate your reward to an eligible charity. If you prefer this option, let us know and we will also match your donation - subject to our discretion. Any rewards that are unclaimed after 12 months will be donated to a charity of our choosing.
Please contact security-vrp@chromium.org with any questions.
******************************
am...@chromium.org <am...@chromium.org> #13
Congratulations ChaobinZhang! The Chrome VRP Panel has decided to award you $2,000 for this report of a heavily mitigated memory corruption bug + $1,000 bisect bonus. Thank you for your efforts in discovering and reporting this issue to us!
zh...@gmail.com <zh...@gmail.com> #14
Thank you very much!
pe...@google.com <pe...@google.com> #15
If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.
Thanks for your time! To disable nags, add Disable-Nags (case sensitive) to the Chromium Labels custom field.
ap...@google.com <ap...@google.com> #16
Branch: refs/branch-heads/6312
commit b7d98516f47fd1d9e4e3b06926a3fbf78e51057a
Author: Rohit Rao <rohitrao@chromium.org>
Date: Thu Mar 28 05:47:23 2024
[ios] Call RemoveObserver when destroying DownloadInternalsUIMessageHandler.
(cherry picked from commit 952757624c6c06c443c487771d070b52719d17b0)
Bug: 326607008
Change-Id: Ifb091ed4917c253ea7d2122d9dfdc94734b1e75e
Reviewed-on:
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1273470}
Reviewed-on:
Auto-Submit: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Mike Dougherty <michaeldo@chromium.org>
Cr-Commit-Position: refs/branch-heads/6312@{#728}
Cr-Branched-From: 6711dcdae48edaf98cbc6964f90fac85b7d9986e-refs/heads/main@{#1262506}
M ios/chrome/browser/webui/ui_bundled/download_internals_ui.cc
pe...@google.com <pe...@google.com> #17
This bug has been closed for more than 14 weeks. Removing issue access restrictions.
Description
VULNERABILITY DETAILS
Bitset:https://chromium-review.googlesource.com/c/chromium/src/+/3072886
DownloadInternalsUIMessageHandler::RegisterMessages
add self as observer into the logger of background download service.However, there is not
RemoveObserver
in~DownloadInternalsUIMessageHandler()
, so the observer will not be removed even though the object of DownloadInternalsUIMessageHandler is freed. The lifetime of DownloadInternalsUIMessageHandler object is bound with WebUI for chrome://download-internals on iOS. New tab with url:chrome://download-internals
and then close it will result in a dangling observer in unchecked observers_ ofdownload::LoggerImpl
.So when the notification happened after the object of |DownloadInternalsUIMessageHandler| is freed, UAF will be triggered.
Fix suggestion:
VERSION
REPRODUCTION CASE
Another:
nc -l 8000
on linux.chrome://download-internals
on iOS, inputhttp://<your-ip>:8000/poc
and click Download, close the tab.There is a POC video in attachements.
FOR CRASHES, PLEASE INCLUDE THE FOLLOWING ADDITIONAL INFORMATION
CREDIT INFORMATION
Reporter credit: ChaobinZhang