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

fix: re-evaluate unpatched CVEs in recalc #1745

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

psegedy
Copy link
Member

@psegedy psegedy commented Jan 9, 2025

even though recalc is triggered by change in repostiries/released erratum, we need to re-evaluate also unpatched cves as it can happen that unpatched CVE becomes patched and we need to remove it from list of unpatched cves

relates to:

RHINENG-15100

RHINENG-15129

Secure Coding Practices Checklist GitHub Link

Secure Coding Checklist

  • Input Validation
  • Output Encoding
  • Authentication and Password Management
  • Session Management
  • Access Control
  • Cryptographic Practices
  • Error Handling and Logging
  • Data Protection
  • Communication Security
  • System Configuration
  • Database Security
  • File Management
  • Memory Management
  • General Coding Practices

@psegedy psegedy requested a review from jdobes January 9, 2025 14:26
Copy link

jira-linking bot commented Jan 9, 2025

@jdobes
Copy link
Member

jdobes commented Jan 9, 2025

/retest

even though recalc is triggered by change in repostiries/released erratum, we need to re-evaluate also unpatched cves as it can happen that unpatched CVE becomes patched and we need to remove it from list of unpatched cves

relates to:

RHINENG-15100

RHINENG-15129
@psegedy psegedy merged commit 85256df into RedHatInsights:master Jan 10, 2025
5 of 6 checks passed
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.

2 participants