Skip to content

parseable/1.5.3-r0: cve remediation#29873

Closed
octo-sts[bot] wants to merge 2 commits intomainfrom
cve-parseable-e6f6271c456c5b86069c1560af89a019
Closed

parseable/1.5.3-r0: cve remediation#29873
octo-sts[bot] wants to merge 2 commits intomainfrom
cve-parseable-e6f6271c456c5b86069c1560af89a019

Conversation

@octo-sts
Copy link
Contributor

@octo-sts octo-sts bot commented Oct 2, 2024

@octo-sts
Copy link
Contributor Author

octo-sts bot commented Oct 2, 2024

Open AI suggestions to solve the build error:

The error message is: "Error: failed to parse the pom file: failed to run cargo update 'Updating crates.io index uses=rust/cargobump
error: failed to select a version for the requirement `lexical-core = "^0.8"`
candidate versions found which didn't match: 1.0.0
location searched: crates.io index
required by package `arrow-json v52.2.0`
... which satisfies dependency `arrow-json = "^52.1.0"` (locked to 52.2.0) of package `parseable v1.5.3 (/home/build/server)`' with error: 'exit status 101'"

1. Open `Cargo.toml` in the `parseable` project.
2. Update `lexical-core` dependency to a compatible version, e.g., `lexical-core = "1.0.0"`.
3. Run `cargo update` to refresh dependencies.
4. If issues persist, check for any other dependencies requiring `lexical-core` and update them accordingly.

@hectorj2f
Copy link
Member

Both CVEs require entries on the advisory file as pending-upstream-fix. Trying to upgrade either of the two vulnerable version conflicts with other dependencies, so we cannot do much here for the moment.

Signed-off-by: Mark McCormick <mark.mccormick@chainguard.dev>
@octo-sts
Copy link
Contributor Author

octo-sts bot commented Oct 5, 2024

Open AI suggestions to solve the build error:

The error message indicates a version conflict with the `lexical-core` dependency in the `parseable` project. To resolve this, update the `lexical-core` dependency in the `Cargo.toml` file to a compatible version, such as `^1.0`, and then run `cargo update` to refresh the dependencies. After making these changes, test the build to ensure everything is working correctly.

@mamccorm
Copy link
Member

mamccorm commented Oct 5, 2024

pending-upstream-fix advisory raised:

@kranurag7
Copy link
Member

closing given wolfi-dev/advisories#8563 is merged.

@kranurag7 kranurag7 closed this Oct 6, 2024
@kranurag7 kranurag7 deleted the cve-parseable-e6f6271c456c5b86069c1560af89a019 branch October 6, 2024 00:43
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.

3 participants