Skip to content

[Issue_44] Renew suppressions for false positives that are still occu…#45

Open
bstansberry wants to merge 1 commit intowildfly-security:mainfrom
bstansberry:Issue_44
Open

[Issue_44] Renew suppressions for false positives that are still occu…#45
bstansberry wants to merge 1 commit intowildfly-security:mainfrom
bstansberry:Issue_44

Conversation

@bstansberry
Copy link
Copy Markdown

…rring for main and 39.0.1

Resolves #44

TBH, as I did this I thought it could be better, but I don't have time today. If a reviewer thinks this PR should do any of these let me know and maybe I will have time. This PR is currently focused on cleaning up results for main and 39.0.1.

  1. For resteasy-spring and resteasy-tracing there are two suppression blocks each that are basically identical and could be combined.
  2. For each of those two, the bigger suppression block lists 7 CVEs, but at least against main and 39.0.1 only 2 are currently producing false positives. So, we could check the results for the older versions and if none of the other CVEs are triggering positives we could trim those from the suppressions.
  3. This PR re-enables some expressions that expired March 11. There are others that expired that day that it doesn't re-enable because there were no false positives against main or 39.0.1. We should check if any of the other version scans are now getting false positives related to those, and if yes, renew the suppression, and if no, remove the suppression.

@bstansberry bstansberry requested a review from a team as a code owner March 26, 2026 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Renew suppressions that expired March 11 that are still triggering reports

1 participant