[UserNotes] Fix UAF in OnNoteCreationDone

UserNoteService was passing a UserNote pointer to the storage layer,
which was making async calls on a separate sequence and dereferencing
the pointer there. This was a potential UAF if the UserNote was
destroyed in the service while the async call was running on the
sequence.

Ideally, the fix would have been to pass a WeakPtr and validate it on
the sequence, but UserNote already has a WeakPtrFactory that creates
SafeRefs for the UserNoteInstance objects, so it is already bound to the
main thread. As such, any WeakPtr it produces cannot be dereferenced on
another sequence.

The proposed fix is thus to create a clone of the UserNote, and pass
that to the storage layer and its sequence. Because AsyncCall() uses
the move constructor to forward args to the other sequence, and the
move constructor of UserNote has been deleted by its WeakPtrFactory,
the clone needs to be a unique_ptr. An alternative would have been to
pass the values of the UserNote properties as function parameters, but
there are up to 8, which would have made the code hard to read and maintain.

Bug: 1363583
Change-Id: I96fed460901cced5148f0c0fb44a7fc21b7618a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3910071
Reviewed-by: Yuheng Huang <yuhengh@chromium.org>
Commit-Queue: Guillaume Jenkins <gujen@google.com>
Cr-Commit-Position: refs/heads/main@{#1054708}
8 files changed
tree: d595560f0d02e67478c60c65a8a9d7c373ee304c
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.