-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Is Litecoin affected by CVE-2018-17144 ? #537
Comments
Hi, we are working on a build of Litecoin 0.16.3 which fixes
CVE-2018-17144. This should be gitian-signed and release within the next
few hours.
…On Wed, 19 Sep 2018 at 13:57, Dmitry Petukhov ***@***.***> wrote:
bitcoin#14247 <bitcoin#14247>
https://nvd.nist.gov/vuln/detail/CVE-2018-17144
It seems that the code that was fixed in bitcoin in ***@***.***
<bitcoin@b8f8019>
still exist in Litecoin's src/validation.cpp:3036
I did not have the time to check this myself, but as a bulk of Litecoin
code is shared with bitcoin, it is very likely that the same bug exist in
Litecoin.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#537>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ACfNuqtWPw2PYFUhECk7oSghp2Lqh2x4ks5ucj8mgaJpZM4WwG1Y>
.
|
@dgpv 0.16.3 which implements a patch for CVE-2018-17144 has been released! If you are running Litecoin Core 0.14.0 to 0.16.2, especially so for economic nodes (exchanges, merchant processor, etc) you should update as soon as possible. 0.16.3 binaries are available on both https://litecoin.org and https://litecoin.com |
hi. @losh11 can you please make I'm using github api to constantly monitor updates of litecoin and it shows that latest version is |
bitcoin#14247
https://nvd.nist.gov/vuln/detail/CVE-2018-17144
It seems that the code that was fixed in bitcoin in bitcoin@b8f8019 still exist in Litecoin's src/validation.cpp:3036
I did not have the time to check this myself, but as a bulk of Litecoin code is shared with bitcoin, it is very likely that the same bug exist in Litecoin.
The text was updated successfully, but these errors were encountered: