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
What would you like to be added: Enhance the existing parse_jvm_release cataloger to address
Why is this needed: These JDK distro's have different versioning schemes and CPE identifiers that prevents them from being correctly identified and matched to known CVEs. The OracleJDK is based on OpenJDK but has its own versioning. The GraalVM releases have community and enterprise editions and also have a change in naming as of the 23 release. The GraalVM releases require the use of GRAALVM_VERSION attribute of the reelase info file.
Additional context:
I have a PR I am preparing in a fork. The chnage is more involved including a schema update and was hoping todiscuss the change and approach with @wagoodman based on the initial implementation.
The text was updated successfully, but these errors were encountered:
Hey @douglasclarke! I know it's short notice here, but we have a community meeting/office hours this week at 12:00 EST if you'd like to join and discuss moving this forward or ways to get the contribution in.
Otherwise @kzantow is probably one of the best contacts on our team for Java related thing as he has the most experience with some of the more nuanced sides of those catalogers.
Summary of discussion on last night's live stream where it was discussed (with more people):
Discussion: Alan Pope presented this Syft issue. The issue report includes a link to a PR in the user's own fork, not against the main Anchore Syft repository.
Problem: It appears to be a version parsing problem in Syft related to GraalVM. The user's PR seems to implement changes to correctly detect the GraalVM version.
Outcome: Alex Goodman will comment on the user's PR in their fork, suggesting they open it against the upstream anchore/syft repository if they are ready for it to be reviewed and potentially merged.
What would you like to be added: Enhance the existing parse_jvm_release cataloger to address
Why is this needed: These JDK distro's have different versioning schemes and CPE identifiers that prevents them from being correctly identified and matched to known CVEs. The OracleJDK is based on OpenJDK but has its own versioning. The GraalVM releases have community and enterprise editions and also have a change in naming as of the 23 release. The GraalVM releases require the use of GRAALVM_VERSION attribute of the reelase info file.
Additional context:
I have a PR I am preparing in a fork. The chnage is more involved including a schema update and was hoping todiscuss the change and approach with @wagoodman based on the initial implementation.
The text was updated successfully, but these errors were encountered: