[COMMITTED] parser: avoid character 0xff being interpreted as (int) -1

[Jose E. Marchesi]

This fixes the following CVEs:
- CVE-2021-46019
- CVE-2021-46022
- CVE-2021-46022

2022-04-16  Jose E. Marchesi  <jemarch@gnu.org>

        CVE-2021-46019
        CVE-2021-46022
        CVE-2021-46022
        * src/rec-parser.c (rec_parse_comment): Avoid 0xff being
        interpreted as (int) -1.
---
 ChangeLog        | 8 ++++++++
 src/rec-parser.c | 2 +-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index 35f0552..11279b3 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,13 @@
 2022-04-16  Jose E. Marchesi  <jemarch@gnu.org>
 
+       CVE-2021-46019
+       CVE-2021-46022
+       CVE-2021-46022
+       * src/rec-parser.c (rec_parse_comment): Avoid 0xff being
+       interpreted as (int) -1.
+
+2022-04-16  Jose E. Marchesi  <jemarch@gnu.org>
+
        * configure.ac: Remove algol68 bindings support.
        * Makefile.am: Remove algol68 from subdirs.
        * algol68: Delete.
diff --git a/src/rec-parser.c b/src/rec-parser.c
index f59bde8..f260410 100644
--- a/src/rec-parser.c
+++ b/src/rec-parser.c
@@ -432,7 +432,7 @@ rec_parse_comment (rec_parser_t parser, rec_comment_t 
*comment)
                 c = '\n';
             }
 
-          if (rec_buf_putc (c, buf) == EOF)
+          if (rec_buf_putc (ci, buf) == EOF)
             {
               /* Out of memory */
               parser->error = REC_PARSER_ENOMEM;
-- 
2.11.0