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

Inform the update situation of CVE-2018-8088 (solved in slf4j 1.7.26 stable) #10

Closed
Neustradamus opened this issue Jan 13, 2022 · 3 comments

Comments

@Neustradamus
Copy link

Neustradamus commented Jan 13, 2022

Dear @qos-ch team,

All websites do not have updated of CVE-2018-8088 situation:

The problem was that you did not want to create a build in 1.7.x with the fix!
It has been fixed in 1.7.26 (stable).

And 1.8.0-beta4 (not 1.8.0-beta2).

I think that today, you understand the problem of vulnerabilities / CVEs.

Thanks in advance.

@ceki
Copy link
Member

ceki commented Jan 13, 2022

Sorry for not updating earlier. .Version 2.0.0 has all the changes from 1.8.x. Thus, CVE-2018-8088 has been fixed both in the 2.0.0 and 1.7.x branches.

@qos-ch qos-ch deleted a comment from Neustradamus Jan 13, 2022
@ceki ceki closed this as completed Jan 13, 2022
Neustradamus referenced this issue in qos-ch/slf4j Jan 13, 2022
@Neustradamus
Copy link
Author

@ceki: At this time, it is always not updated in CVE websites.

No information about 1.7.26 (stable) and 1.8.0-beta4 (unstable).

When it will be good?

@ceki
Copy link
Member

ceki commented Jan 26, 2022

@Neustradamus I have just asked them to update the CVE in question.

Have not heard back 24 hours later.

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