Google Go 缓冲区错误漏洞

Google Go is a statically strongly-typed, compiled, concurrently-typed, and garbage collected programming language from the U.S. company Google Google. A security vulnerability exists in ImportedSymbols, which stems from importing symbols for Open or OpenFat in Go's debug macho and accessing memo...

CVE-2021-41771

ImportedSymbols in debug/macho for Open or OpenFat in Go before 1.16.10 and 1.17.x before 1.17.3 Accesses a Memory Location After the End of a Buffer, aka an out-of-bounds slice situation...

CVE-2021-41771: Improper Restriction of Operations within the Bounds of a Memory Buffer

ImportedSymbols in debug/macho for Open or OpenFat in Go before 1.16.10 and 1.17.x before 1.17.3 Accesses a Memory Location After the End of a Buffer, aka an out-of-bounds slice situation...

CVE-2021-41771

ImportedSymbols in debug/macho for Open or OpenFat in Go before 1.16.10 and 1.17.x before 1.17.3 Accesses a Memory Location After the End of a Buffer, aka an out-of-bounds slice situation...

CVE-2021-41771

ImportedSymbols in debug/macho for Open or OpenFat in Go before 1.16.10 and 1.17.x before 1.17.3 Accesses a Memory Location After the End of a Buffer, aka an out-of-bounds slice situation...

CVE-2021-41771

An out of bounds read vulnerability was found in debug/macho of the Go standard library. When using the debug/macho standard library stdlib and malformed binaries are parsed using Open or OpenFat, it can cause golang to attempt to read outside of a slice array causing a panic when calling...

PT-2021-23401

Name of the Vulnerable Software and Affected Versions Go versions prior to 1.16.10 Go versions 1.17.x prior to 1.17.3 Description The issue is related to an out-of-bounds slice situation where ImportedSymbols in debug/macho accesses a memory location after the end of a buffer. This can occur when...

go -- multiple vulnerabilities

The Go project reports: debug/macho fails out when loading a file that contains a dynamic symbol table command that indicates a larger number of symbols than exist in the loaded symbol table. Previously, opening a zip with Reader.Open could result in a panic if the zip contained a file whose name...