Skip to content
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

Vulnerability Detector - Port "Adjustment of vulnerability descriptions" from 4.10.0 #26130

Open
3 tasks
sebasfalcone opened this issue Oct 3, 2024 · 5 comments · May be fixed by #26557
Open
3 tasks

Vulnerability Detector - Port "Adjustment of vulnerability descriptions" from 4.10.0 #26130

sebasfalcone opened this issue Oct 3, 2024 · 5 comments · May be fixed by #26557
Assignees
Labels
level/task type/enhancement New feature or request

Comments

@sebasfalcone
Copy link
Member

Description

This issue aims to port the changes related to the ADP descriptive information usage, from 4.10.0 into 5.0.0:

This will ensure consistency and accuracy on the descriptive information from generated events and alerts for the Vulnerability Detector module

Important

We are not going to update the store model, this includes:

  • updateCVEDescription.hpp
  • databaseFeedManager.hpp
    Instead, we are going to rely solely on the generated content from 4.10.0 to serve this functionality

DoD

  • Changes ported
  • Updated testing
  • Tested behaviour
@sebasfalcone sebasfalcone added type/enhancement New feature or request level/task labels Oct 3, 2024
@sebasfalcone sebasfalcone self-assigned this Oct 3, 2024
@wazuhci wazuhci moved this to Triage in Release 5.0.0 Oct 3, 2024
@wazuhci wazuhci moved this from Triage to Backlog in Release 5.0.0 Oct 4, 2024
@sebasfalcone
Copy link
Member Author

sebasfalcone commented Oct 23, 2024

Update

Remember to:

  • Add the vulnerability source field into the API response
  • Update the efficacy tests to retrieve this field

@wazuhci wazuhci moved this from Backlog to In progress in Release 5.0.0 Oct 25, 2024
@sebasfalcone sebasfalcone removed their assignment Oct 25, 2024
@wazuhci wazuhci moved this from In progress to Backlog in Release 5.0.0 Oct 25, 2024
@sebasfalcone sebasfalcone self-assigned this Oct 25, 2024
@wazuhci wazuhci moved this from Backlog to In progress in Release 5.0.0 Oct 25, 2024
@sebasfalcone sebasfalcone linked a pull request Oct 25, 2024 that will close this issue
@sebasfalcone sebasfalcone linked a pull request Oct 25, 2024 that will close this issue
@sebasfalcone
Copy link
Member Author

ETA updated

Due to higger priority issues:

@wazuhci wazuhci moved this from In progress to On hold in Release 5.0.0 Oct 29, 2024
@wazuhci wazuhci moved this from On hold to In progress in Release 5.0.0 Nov 1, 2024
@wazuhci wazuhci moved this from In progress to On hold in Release 5.0.0 Nov 1, 2024
@sebasfalcone
Copy link
Member Author

sebasfalcone commented Nov 8, 2024

Update

Still working on higher priority issues

2 similar comments
@sebasfalcone
Copy link
Member Author

sebasfalcone commented Nov 15, 2024

Update

Still working on higher priority issues

@sebasfalcone
Copy link
Member Author

Update

Still working on higher priority issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task type/enhancement New feature or request
Projects
Status: On hold
Development

Successfully merging a pull request may close this issue.

1 participant