-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Patch protobuf CVE-2022-1941 #25490
Patch protobuf CVE-2022-1941 #25490
Conversation
0a43aa5
to
31a947d
Compare
It looks like we need to update pigweed as well. PR for that is here: google/pigweed#12. |
PR #25490: Size comparison from 6dd5294 to b51076e Full report (1 build for cc32xx)
|
b51076e
to
f8b6d47
Compare
PR #25490: Size comparison from d44b6a6 to f8b6d47 Decreases (1 build for cc32xx)
Full report (3 builds for cc32xx, qpg)
|
f8b6d47
to
6e3e914
Compare
Some tooling is using a version of protobuf with a known vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2022-1941 Change requirements to use the patched version. Fixes project-chip#25489
6e3e914
to
1d07436
Compare
PR #25490: Size comparison from 4203370 to 1d07436 Full report (1 build for cc32xx)
|
I succeeded in getting the protobuf patch upstreamed to https://pigweed.googlesource.com/pigweed/pigweed. However, pulling in the newest upstream pigweed now breaks a couple of our builds. Do we have any resident pigweed experts? |
#25351 is working towards that. https://pigweed.dev/docs/getting_started.html says there is a chatroom as well for direct asking. Wyatt is the owner for #25351 |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This stale pull request has been automatically closed. Thank you for your contributions. |
Some tooling is using a version of protobuf with a known vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2022-1941
Change requirements to use the patched version.
Fixes #25489