Skip to content

Possible vulnerability in Jcommander version 1.35 #5981

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

Open
JosuaCarl opened this issue Apr 17, 2025 · 1 comment
Open

Possible vulnerability in Jcommander version 1.35 #5981

JosuaCarl opened this issue Apr 17, 2025 · 1 comment

Comments

@JosuaCarl
Copy link

Importing testImplementation "io.nextflow:nextflow:24.10.5" results in the following warning from IntelliJ:

Dependency maven:com.beust:jcommander:1.35 is vulnerable

With the details:

WS-2019-0490, Score: 8.1
Inclusion of Functionality from Untrusted Control Sphere vulnerability found in jcommander before 1.75. jcommander resolving dependencies over HTTP instead of HTTPS.
Details

The following corresponding code is found currently in Nextflow:

api "com.beust:jcommander:1.35"

The suggested fix is a version bump to 1.75 as a safe version.

@pditommaso
Copy link
Member

Provided We should look into solving this, unfortunately it's not an simple drop-in replacement since this that version brings some braking changes.

Worth also noting that's (was) a building time issue, not a run-time one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants