News for hackers. Stuff that matters.
Re:Glibc Buffer Overflow in Iconv by thenickdude on Sunday April 21, 2024 @01:15PM (#40107388)
Or else edit /usr/lib/x86_64-linux-gnu/gconv/gconv-modules and comment out this section:

  #       from                    to                      module          cost
  alias  ISO2022CNEXT//          ISO-2022-CN-EXT//
  module ISO-2022-CN-EXT//       INTERNAL                ISO-2022-CN-EXT 1
  module INTERNAL                ISO-2022-CN-EXT//       ISO-2022-CN-EXT 1
Then run "iconvconfig" to rebuild the iconv cache. This disables that charset completely.
Re:Glibc Buffer Overflow in Iconv by LXicon on Sunday April 21, 2024 @02:40PM (#40108089)
As a test on various distros, I ran iconv -l |grep 2022 |grep -i cn

and it listed ISO-2022-CN-EXT// and ISO2022CNEXT// before I made any changes. After editing the modules and running iconvconfig the command no longer showed those charsets.

This was handy since the alma8 has a /usr/lib64/gconv/gconv-modules file but the file to edit was /usr/lib64/gconv/gconv-modules.d/gconv-modules-extra.conf

Re:Glibc Buffer Overflow in Iconv by voyagerfan5761 on Sunday April 21, 2024 @05:27PM (#40109391)
Thanks a bunch to you and thenickdude for the test command and config to change.

I have an old VPS that isn't worth trying to update to a newer OS image, because I'm already (slowly) migrating things off of it before the current paid-up term expires, but it definitely won't get the newer glibc. Disabling the vulnerable character encoding works for me, since no legitimate user of the server will need these conversion pairs.