diff options
Diffstat (limited to 'main/musl/0001-fix-memory-corruption-in-regcomp-with-backslash-foll.patch')
| -rw-r--r-- | main/musl/0001-fix-memory-corruption-in-regcomp-with-backslash-foll.patch | 33 |
1 files changed, 0 insertions, 33 deletions
diff --git a/main/musl/0001-fix-memory-corruption-in-regcomp-with-backslash-foll.patch b/main/musl/0001-fix-memory-corruption-in-regcomp-with-backslash-foll.patch deleted file mode 100644 index 6354d7c50f..0000000000 --- a/main/musl/0001-fix-memory-corruption-in-regcomp-with-backslash-foll.patch +++ /dev/null @@ -1,33 +0,0 @@ -From 39dfd58417ef642307d90306e1c7e50aaec5a35c Mon Sep 17 00:00:00 2001 -From: Rich Felker <dalias@aerifal.cx> -Date: Fri, 20 Mar 2015 18:06:04 -0400 -Subject: [PATCH] fix memory-corruption in regcomp with backslash followed by - high byte - -the regex parser handles the (undefined) case of an unexpected byte -following a backslash as a literal. however, instead of correctly -decoding a character, it was treating the byte value itself as a -character. this was not only semantically unjustified, but turned out -to be dangerous on archs where plain char is signed: bytes in the -range 252-255 alias the internal codes -4 through -1 used for special -types of literal nodes in the AST. ---- - src/regex/regcomp.c | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/src/regex/regcomp.c b/src/regex/regcomp.c -index 4cdaa1e..bce6bc1 100644 ---- a/src/regex/regcomp.c -+++ b/src/regex/regcomp.c -@@ -847,7 +847,7 @@ static reg_errcode_t parse_atom(tre_parse_ctx_t *ctx, const char *s) - } else { - /* extension: accept unknown escaped char - as a literal */ -- node = tre_ast_new_literal(ctx->mem, *s, *s, ctx->position); -+ goto parse_literal; - } - ctx->position++; - } --- -2.3.3 - |