-
Notifications
You must be signed in to change notification settings - Fork 805
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
Protect Status: Combine multiple vulnerabilities for the same extension into single threat objects #40863
base: trunk
Are you sure you want to change the base?
Protect Status: Combine multiple vulnerabilities for the same extension into single threat objects #40863
Conversation
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Follow this PR Review Process:
Still unsure? Reach out in #jetpack-developers for guidance! Jetpack plugin: The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Backup plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Boost plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Search plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Social plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Starter Plugin plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Protect plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Videopress plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
8128367
to
51ecb63
Compare
projects/packages/protect-models/changelog/protect-status-combine-vulns-into-extension-threat
Outdated
Show resolved
Hide resolved
5b9c416
to
86e2a9f
Compare
32064df
to
fb06d1e
Compare
…erable extension threat changelog minor adjustments changelog add source to generator minor adjustments Add typed params minor adjustments use generator for core vulns threat update tests, minor adjustments adjust tests Fix phan issues add jetpack-redirect dep fix tests update lock files changelog Update projects/packages/protect-models/changelog/protect-status-combine-vulns-into-extension-threat
fb06d1e
to
ca8e549
Compare
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.
Works as described and tests all continue to pass!
One minor change requested for the Vulnerability_Model
documentation.
One other thing worth noting, I see that every entry in the new vulnerabilities
array has an introduced_in
prop that is set to null
- seems that the Vulnerability_Model
defines this value but we maybe aren't explicitly setting it, that or its just a complete coincidence that each of the vulns for the threat I added don't have that prop set.
public $id; | ||
|
||
/** | ||
* Threat Title. |
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.
* Threat Title. | |
* Vulnerability Title. |
I suspect this model was copied over from the Threat_Model
, we should update the documentation to reflect the variation.
Updates the
protect-status
package to group vulnerabilities by extension (i.e. one threat per vulnerable extension).Proposed changes:
Vulnerability_Model
class.Threat_Model::$vulnerabilities
property.Protect_Status
to generate a singleThreat_Model
per vulnerable extension, with the relevant vulnerabilities included as a property of the threat.Other information:
Jetpack product discussion
peb6dq-3ma-p2
Does this pull request change what data or activity we track or use?
No
Testing instructions:
jetpack-protect/v1/status
with a free plan:plugins
,themes
, andcore
properties.threats
property.window.jetpackProtectInitialState
, or the TanStack Query developer tools.