You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please keep any sensitive details in Google Drive.
Date of report: 12/6/2022 Severity: Low Due date: 03/06/2022
Due date is based on severity and described in RA-5. 15-days for Critical, 30-days for High, and 90-days for Moderate and lower.
Analysis has been performed and an issue has been linked to address other occurrences for this class of vulnerability* (link)
* When a finding is identified, we create two issues. One to address the specific instance identified in the report. The other is to identify and address all other occurrences of this vulnerability within the application.
Okay, I'll try to implement it and make sure there's no funny business like keys being recreated in a way that would cause problems. Thanks for the quick response! @mogul
Please keep any sensitive details in Google Drive.
Date of report: 12/6/2022
Severity: Low
Due date: 03/06/2022
Due date is based on severity and described in RA-5. 15-days for Critical, 30-days for High, and 90-days for Moderate and lower.
* When a finding is identified, we create two issues. One to address the specific instance identified in the report. The other is to identify and address all other occurrences of this vulnerability within the application.
Snyk Link
Detailed paths
Introduced through:
input › resource › aws_kms_key[zone] › enable_key_rotation
This issue is...
The impact of this is...
You can resolve it by...
enable_key_rotation
attribute totrue
The text was updated successfully, but these errors were encountered: