golang-go.crypto was recently updated with a fix for CVE-2019-11840. This in turn requires all packages that use the affected code to be recompiled in order to pick up the security fix. . - ------------------------------------------------------------------------- Debian LTS Advisory DLA-2527-1
CVE-2019-11840 An issue was discovered in supplementary Go cryptography libraries, aka golang-googlecode-go-crypto. If more than 256 GiB of keystream is . - ------------------------------------------------------------------------- Debian LTS Advisory DLA-2402-1
A flaw was found in the amd64 implementation of salsa20. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. . Package : golang-go.crypto Version : 0.0~hg190-1+deb8u1 CVE ID : CVE-2019-11840 A flaw was found in the amd64 implementation of salsa20. If more than 256 GiB of keystream is generated, or if the counter otherwise grows greater than 32 bits, the amd64 implementation will first generate incorrect output, and then cycle back to previously generated keystream. For Debian 8 "Jessie", this problem has been fixed in version 0.0~hg190-1+deb8u1. obfs4proxy has been rebuilt as version 0.0.3-2+deb8u1. We recommend that you upgrade your golang-golang-x-crypto-dev and obfs4proxy packages, and rebuild any software using golang-golang-x-crypto-dev. Further information about Debian LTS security advisories, how to apply these updates to your system and frequently asked questions can be found at: https://wiki.debian.org/LTS . Revise golang-go.crypto on Debian LTS to address keystream vulnerability impacting amd64 version. Essential security patch required.. Debian LTS, golang-go.crypto, keystream flaw, security update, salsa20 implementation. . Severity: Critical. LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.