Your message dated Mon, 19 May 2025 17:46:38 +0000 with message-id <e1uh4zs-002s57...@respighi.debian.org> and subject line unblock postgresql-17 has caused the Debian Bug report #1106048, regarding unblock: postgresql-17/17.5-1 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1106048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal X-Debbugs-Cc: postgresql...@packages.debian.org Control: affects -1 + src:postgresql-17 User: release.debian....@packages.debian.org Usertags: unblock Please unblock package postgresql-17 [ Reason ] New upstream version, fixes CVE-2025-4207. [ Tests ] Extensive upstream and postgresql-common tests. unblock postgresql-17/17.5-1 postgresql-17 (17.5-1) unstable; urgency=medium * New upstream version 17.5. + Avoid one-byte buffer overread when examining invalidly-encoded strings that are claimed to be in GB18030 encoding (Noah Misch, Andres Freund) While unlikely, a SIGSEGV crash could occur if an incomplete multibyte character appeared at the end of memory. This was possible both in the server and in libpq-using applications. (CVE-2025-4207) -- Christoph Berg <m...@debian.org> Tue, 06 May 2025 17:55:19 +0200 Christoph
--- End Message ---
--- Begin Message ---Unblocked.
--- End Message ---
