Skip to content

neo4j-5.26/5.26.0-r0: cve remediation#38323

Closed
octo-sts[bot] wants to merge 1 commit intomainfrom
cve-neo4j-5.26-aba36e99d83d3d459ebf7b1fb5541320
Closed

neo4j-5.26/5.26.0-r0: cve remediation#38323
octo-sts[bot] wants to merge 1 commit intomainfrom
cve-neo4j-5.26-aba36e99d83d3d459ebf7b1fb5541320

Conversation

@octo-sts
Copy link
Contributor

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

@debasishbsws
Copy link
Member

The CVE is sill there

@debasishbsws
Copy link
Member

  - timestamp: 2024-11-20T13:04:12Z
    type: pending-upstream-fix
    data:
      note: |
        This vulnerability relates to the 'jetty-http' dependency, which is fixed in v12.0.12 and later.
        Unfortunately, we are not able to remediate this CVE, as bumping this dependency version results in build failures.
        Specifically, there are version conflicts between the various jetty dependencies. Attempting to bump the related dependencies to the same version, results in different build issues.
        Another component: 'jetty-servlet', has also been relocated to a new location in maven central: https://mvnrepository.com/artifact/org.eclipse.jetty/jetty-servlet. This requires additional code changes.
        All attempts were made to chain up the required changes, but to no avail. Pending fix from upstream.

@debasishbsws
Copy link
Member

@hectorj2f hectorj2f closed this Jan 6, 2025
@hectorj2f hectorj2f deleted the cve-neo4j-5.26-aba36e99d83d3d459ebf7b1fb5541320 branch January 6, 2025 08:05
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.

2 participants