[GHSA-574f-3g2m-x479] Use of a Broken or Risky Cryptographic Algorithm...#7767
Conversation
There was a problem hiding this comment.
Pull request overview
Updates GHSA-574f-3g2m-x479’s advisory content to better describe the cryptographic impact and to enumerate affected Maven artifacts, along with revised CVSS v4 and severity metadata.
Changes:
- Added a
summaryand expandeddetailsdescribing the CTR counter wrap/keystream reuse impact and fix behavior. - Populated
affectedwith Maven coordinates and version ranges for multiple Bouncy Castle provider artifacts. - Updated CVSS v4 vector and adjusted
database_specific.severity.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "type": "ECOSYSTEM", | ||
| "events": [ | ||
| { | ||
| "introduced": "1.59" |
There was a problem hiding this comment.
Maven Central does not yet list a published 1.84 version for this package. See https://repo1.maven.org/maven2/org/bouncycastle/bcprov-jdk15on. Therefore, we can't be sure whether a future 1.84 version would fix the vulnerability.
|
👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the |
db420c1
into
simon-reisinger-dynatrace/advisory-improvement-7767
|
Hi @simon-reisinger-dynatrace! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
Updates
Comments