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

Vulnerabilities CVE-2024-43598 & sonatype-2024-013191 found in the latest v4.5.0 #6759

Closed
OlgasAcc opened this issue Dec 15, 2024 · 5 comments
Labels

Comments

@OlgasAcc
Copy link

OlgasAcc commented Dec 15, 2024

Description

Hello,
Our Sonatype security scanner has detected CVE sonatype-2024-013191 and https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43598 in the latest version of the lightgbm– v4.5.0 (and in the current version we use for our python services - v4.0.0).

Image Image

Based on the Sonatype description, there is no non-vulnerable version available.
Could you please provide the necessary fix and release?

Thanks

Image
@OlgasAcc OlgasAcc changed the title Vulnerability sonatype-2024-013191 found in the latest v4.5.0 Vulnerabilities CVE-2024-43598 & sonatype-2024-013191 found in the latest v4.5.0 Dec 15, 2024
@jameslamb
Copy link
Collaborator

Thanks for using LightGBM.

Please:

  1. search the issues here before posting (this is identical to Status of CVE-2024-43598? #6750 )
  2. do not post about security vulnerabilities publicly (see https://github.com/microsoft/LightGBM/blob/master/SECURITY.md)

A fix has been merged, we will try to do a release in the next few weeks.

The vulnerability only affects distributed (multi-machine) training, so if you don't do that you can safely ignore it.

@OlgasAcc
Copy link
Author

Hi @jameslamb thanks a lot for the quick response and the fix. And my apologies for this confusion.
We'll be looking forward for the next released version of LightGBM.

Regards,
Olga

@MarkJacksonRG
Copy link

Please release it so the community can use the fix!

@OlgasAcc
Copy link
Author

@jameslamb could you please provide ETA of the next release (which will contain the mentioned fix)? Thanks

@jameslamb
Copy link
Collaborator

We will do a release when we can. I do not have an ETA. We understand.

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

No branches or pull requests

3 participants