view pixmaps/quest.xpm @ 33780:377ed6ab612c v9.0.2110

patch 9.0.2110: [security]: overflow in ex address parsing Commit: https://github.com/vim/vim/commit/060623e4a3bc72b011e7cd92bedb3bfb64e06200 Author: Christian Brabandt <cb@256bit.org> Date: Tue Nov 14 21:33:29 2023 +0100 patch 9.0.2110: [security]: overflow in ex address parsing Problem: [security]: overflow in ex address parsing Solution: Verify that lnum is positive, before substracting from LONG_MAX [security]: overflow in ex address parsing When parsing relative ex addresses one may unintentionally cause an overflow (because LONG_MAX - lnum will overflow for negative addresses). So verify that lnum is actually positive before doing the overflow check. Signed-off-by: Christian Brabandt <cb@256bit.org>
author Christian Brabandt <cb@256bit.org>
date Thu, 16 Nov 2023 22:15:12 +0100
parents 3fc0f57ecb91
children
line wrap: on
line source

/* XPM */
static char * quest_xpm[] = {
/* width height ncolors cpp [x_hot y_hot] */
"34 34 4 1 0 0",
/* colors */
" 	s none	m none	c none",
".	s bottomShadowColor	m black	c #5D6069",
"X	s iconColor2	m white	c #FFFFFF",
"o	s iconColor1	m black	c #000000",
/* pixels */
"                                  ",
"            ........              ",
"         ...XXXXXXXX...           ",
"       ..XXXXXXXXXXXXXX..         ",
"      .XXXXXXXXXXXXXXXXXX.        ",
"     .XXXXXXXXoooooXXXXXXXo       ",
"    .XXXXXXXXoXXXXooXXXXXXXo      ",
"   .XXXXXXXXoooXXXXooXXXXXXXo     ",
"  .XXXXXXXXXooooXXXooXXXXXXXXo    ",
"  .XXXXXXXXXXooXXXoooXXXXXXXXo.   ",
" .XXXXXXXXXXXXXXXooooXXXXXXXXXo.  ",
" .XXXXXXXXXXXXXXooooXXXXXXXXXXo.  ",
" .XXXXXXXXXXXXXoooooXXXXXXXXXXo.. ",
" .XXXXXXXXXXXXoooooXXXXXXXXXXXo.. ",
" .XXXXXXXXXXXXoooXXXXXXXXXXXXXo.. ",
" .XXXXXXXXXXXXooXXXXXXXXXXXXXXo.. ",
" .XXXXXXXXXXXXoXXXXXXXXXXXXXXXo.. ",
"  .XXXXXXXXXXXoXXXXXXXXXXXXXXo... ",
"  .XXXXXXXXXXXXXXXXXXXXXXXXXXo... ",
"   .XXXXXXXXXXooXXXXXXXXXXXXo...  ",
"    oXXXXXXXXooooXXXXXXXXXXo....  ",
"     oXXXXXXXXooXXXXXXXXXXo....   ",
"      oXXXXXXXXXXXXXXXXXXo....    ",
"       ooXXXXXXXXXXXXXXoo....     ",
"        .oooXXXXXXXXooo.....      ",
"         ...oooXXXXo.......       ",
"           ....oXXXo.....         ",
"              .oXXXo..            ",
"                oXXo..            ",
"                 oXo..            ",
"                  oo..            ",
"                   ...            ",
"                    ..            ",
"                                  "};