Mercurial > vim
view pixmaps/tb_print.xpm @ 33915:a49ae967e9ed v9.0.2158
patch 9.0.2158: [security]: use-after-free in check_argument_type
Commit: https://github.com/vim/vim/commit/0f28791b215bd4c22ed580839409c2f7d39d8140
Author: Christian Brabandt <cb@256bit.org>
Date: Mon Dec 11 17:53:25 2023 +0100
patch 9.0.2158: [security]: use-after-free in check_argument_type
Problem: [security]: use-after-free in check_argument_type
Solution: Reset function type pointer when freeing the function type
list
function pointer fp->uf_func_type may point to the same memory, that was
allocated for fp->uf_type_list. However, when cleaning up a function
definition (e.g. because it was invalid), fp->uf_type_list will be
freed, but fp->uf_func_type may still point to the same (now) invalid
memory address.
So when freeing the fp->uf_type_list, check if fp->func_type points to
any of those types and if it does, reset the fp->uf_func_type pointer to
the t_func_any (default) type pointer
closes: #13652
Signed-off-by: Christian Brabandt <cb@256bit.org>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Mon, 11 Dec 2023 18:00:03 +0100 |
parents | af1bcb9a13c0 |
children |
line wrap: on
line source
/* XPM */ static char * tb_print_xpm[] = { /* width height ncolors cpp [x_hot y_hot] */ "18 18 7 1 0 0", /* colors */ " s none m none c none", ". s iconColor1 m black c #000000", "X s iconColor2 m none c #FFFFFF", "o s iconGray2 m none c #bdbdbd", "O s iconGray5 m black c #737373", "+ s bottomShadowColor m black c #5D6069", "@ c #FF1144", /* pixels */ " ....... ", " .XXXXX.. ", " .XXXXX.X. ", " .XXXXX.... ", " .XXXXXXXX. ", " .XXXXXXXX. ", " ..XXXXXXXX.. ", " .XXXXXXXX.O ", "................ ", ".XXXXXXXXXXXXXO. ", ".X@@ooooooooooO.O ", ".XooooooooooooO.O ", ".XooooooooooooO.O ", "................O ", " .OOOOOOOOOOOO.OO ", " ..............O ", " OOOOOOOOOOOOO ", " "};