commit 27f85ddbff8fb2a79a2bc7f0616d0051c1b7052c
author CPE Updater <chops-security-cronjobs-cpesuggest@prod.google.com> Tue Jul 29 16:52:33 2025
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Tue Jul 29 16:52:33 2025
tree e59b973bbbec630e3e7db6453715a7370ba43e04
parent 0092e82b82c1a0de23f7897808ab4fea4627e9a6

[cpesuggest] Add CPE prefix for third_party/maven/3pp/3pp.pb.

To verify the correctness of the suggested CPE Prefix, please follow the
steps below:
1. Visit the National Vulnerability Database (NVD) page for the suggested
   CPE Prefix here: https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.2&keyword=cpe:/a:apache:maven&status=FINAL%2CDEPRECATED
2. Check whether the third-party dependency for which the CPE Prefix is
   suggested matches the project listed in the NVD page.
3. If the open source project matches and the CPE prefix is not deprecated,
   please Code-Review+1 and submit if you have enough votes.
4. If the open source project does not match or if the CPE prefix is
   deprecated, please add the incorrect suggestion to go/ignored_cpes_textproto
   and add the reason why the suggestion is incorrect.

Adding CPE prefixes to a README.chromium file is recommended practice [1] to
enable automated vulnerability monitoring. For more information on how CPE
prefixes are used see the Chromium Third Party docs [2].

[1] https://chromium.googlesource.com/chromium/src/+/HEAD/third_party/README.chromium.template

[2] https://chromium.googlesource.com/chromium/src/+/HEAD/docs/adding_to_third_party.md#add-a-readme_chromium

Bug: b/293810648
Change-Id: I45622972b373a6bb9d85cae578bdf26fc33acf44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6788081
Commit-Queue: Peter Wen <wnwen@chromium.org>
Auto-Submit: CPE Updater <chops-security-cronjobs-cpesuggest@prod.google.com>
Reviewed-by: Joey Scarr <jsca@google.com>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1493606}