Source: binaryen Version: 64-1 Severity: important Tags: security upstream Hi,
The following vulnerabilities were published for binaryen. I was initially confused about the intersting versioning scheme, but the issues are present in 64-1 and I think all of those fixed in 65 upstream (but please double-check the referenced upstream issues and fixing commits as commited by upstream). CVE-2019-7151[0]: | A NULL pointer dereference was discovered in | wasm::Module::getFunctionOrNull in wasm/wasm.cpp in Binaryen 1.38.22. A | crafted input can cause segmentation faults, leading to | denial-of-service, as demonstrated by wasm-opt. CVE-2019-7152[1]: | A heap-based buffer over-read was discovered in | wasm::WasmBinaryBuilder::processFunctions() in wasm/wasm-binary.cpp | (when calling wasm::WasmBinaryBuilder::getFunctionIndexName) in | Binaryen 1.38.22. A crafted input can cause segmentation faults, | leading to denial-of-service, as demonstrated by wasm-opt. CVE-2019-7153[2]: | A NULL pointer dereference was discovered in | wasm::WasmBinaryBuilder::processFunctions() in wasm/wasm-binary.cpp | (when calling wasm::WasmBinaryBuilder::getFunctionIndexName) in | Binaryen 1.38.22. A crafted input can cause segmentation faults, | leading to denial-of-service, as demonstrated by wasm-opt. CVE-2019-7154[3]: | The main function in tools/wasm2js.cpp in Binaryen 1.38.22 has a | heap-based buffer overflow because Emscripten is misused, triggering an | error in cashew::JSPrinter::printAst() in | emscripten-optimizer/simple_ast.h. A crafted input can cause | segmentation faults, leading to denial-of-service, as demonstrated by | wasm2js. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-7151 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7151 [1] https://security-tracker.debian.org/tracker/CVE-2019-7152 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7152 [2] https://security-tracker.debian.org/tracker/CVE-2019-7153 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7153 [3] https://security-tracker.debian.org/tracker/CVE-2019-7154 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7154 Regards, Salvatore
