Use of unsafe calls should be audited
46 b := blade.Blade{}
47 setField := func(name string, value interface{}) {
48 field := reflect.ValueOf(&b).Elem().FieldByName(name)
49 reflect.NewAt(field.Type(), unsafe.Pointer(field.UnsafeAddr())).Elem().Set(reflect.ValueOf(value)) 50 }
51 setField("cwl", cloudwatchlogs.New(session))
52 setField("config", &sawConfig)
Description
Package unsafe contains operations that step around the type safety of Go
programs and may be non-portable. Also note that unsafe package is not
supported by Go 1 compatibility guidelines.
Using the unsafe package in Go gives you low-level memory management and many C language
strengths but provides flexibility to your attacker's application. The pointer arithmetic
is one example of an unsafe package used for the data leak, memory corruption, or even
execution of the attacker's script. Also, it would be best to remember that Go 1 compatibility
guidelines do not protect the "unsafe" package.
Bad practice
package main
import (
"fmt"
"unsafe"
)
type Fake struct{}
func (Fake) Good() {}
func main() {
unsafeM := Fake{}
unsafeM.Good()
intArray := [...]int{1, 2}
fmt.Printf("
intArray: %v
", intArray)
intPtr := &intArray[0]
fmt.Printf("
intPtr=%p, *intPtr=%d.
", intPtr, *intPtr)
addressHolder := uintptr(unsafe.Pointer(intPtr)) + unsafe.Sizeof(intArray[0])
intPtr = (*int)(unsafe.Pointer(addressHolder))
fmt.Printf("
intPtr=%p, *intPtr=%d.
", intPtr, *intPtr)
}