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

trino/467-r0: cve remediation #38101

Closed
wants to merge 4 commits into from

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Dec 20, 2024

Copy link
Contributor Author

octo-sts bot commented Dec 20, 2024

Gen AI suggestions to solve the build error:

• Detected Error:

[ERROR] Failed to execute goal on project trino-plugin-toolkit: Could not resolve dependencies for project io.trino:trino-plugin-toolkit:jar:467
[ERROR] dependency: ch.qos.logback:logback-core:jar:1.15.13 (import)
[ERROR] Could not find artifact ch.qos.logback:logback-core:jar:1.15.13 in central

• Error Category: Dependency

• Failure Point: Maven dependency resolution during package build

• Root Cause Analysis: The pombump tool is trying to upgrade logback-core to version 1.15.13, which doesn't exist. The current latest version of logback-core is 1.4.14.

• Suggested Fix: Modify the pombump version constraint in the pipeline:

  1. Add a version constraint override in the uses: maven/pombump step:
  - uses: maven/pombump
    with:
      version-constraints:
        - "ch.qos.logback:logback-core:1.4.14"

• Explanation: The pombump tool is attempting to use a non-existent version (1.15.13) of logback-core. By explicitly setting the version to the latest stable release (1.4.14), the dependency resolution should succeed.

• Additional Notes:

  • Logback versioning follows semantic versioning
  • Version 1.4.x is the current stable release line
  • The attempted version 1.15.13 appears to be an invalid version number

• References:

Signed-off-by: Mark McCormick <mark.mccormick@chainguard.dev>
Signed-off-by: Mark McCormick <mark.mccormick@chainguard.dev>
Signed-off-by: Mark McCormick <mark.mccormick@chainguard.dev>
@mamccorm
Copy link
Member

Closing as there is a newer version (dup) of this update, which includes both the CVEs

@mamccorm mamccorm closed this Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant