comparison src/version.c @ 33262:6eac4f616293 v9.0.1899

patch 9.0.1899: potential buffer overflow in PBYTE macro Commit: https://github.com/vim/vim/commit/ffb13674d1af1c90beb229867ec989e4fb232df3 Author: Christian Brabandt <cb@256bit.org> Date: Fri Sep 15 20:22:02 2023 +0200 patch 9.0.1899: potential buffer overflow in PBYTE macro Problem: potential buffer overflow in PBYTE macro Solution: Check returned memline length closes: #13083 the PBYTE macro is used to put byte c at a position lp of the returned memline. However, in case of unexpected errors ml_get_buf() may return either "???" or an empty line in which case it is quite likely that we are causing a buffer overrun. Therefore, switch the macro PBYTE (which is only used in ops.c anyhow) to a function, that verifies that we will only try to access within the given length of the buffer. Also, since the macro is only used in ops.c, move the definition from macros.h to ops.c Signed-off-by: Christian Brabandt <cb@256bit.org>
author Christian Brabandt <cb@256bit.org>
date Fri, 15 Sep 2023 20:30:07 +0200
parents aba1fa2b7d1e
children fda04a2e9dee
comparison
equal deleted inserted replaced
33261:cc83932e459d 33262:6eac4f616293
697 NULL 697 NULL
698 }; 698 };
699 699
700 static int included_patches[] = 700 static int included_patches[] =
701 { /* Add new patch number below this line */ 701 { /* Add new patch number below this line */
702 /**/
703 1899,
702 /**/ 704 /**/
703 1898, 705 1898,
704 /**/ 706 /**/
705 1897, 707 1897,
706 /**/ 708 /**/