Package: release.debian.org
User: [email protected]
Usertags: unblock
Dear Release Team,
Please consider pre-approval for redis 5:8.0.2-2
redis (5:8.0.2-2) unstable; urgency=high
* CVE-2025-32023: An authenticated user may have used a specially-crafted
string to trigger a stack/heap out-of-bounds write during hyperloglog
operations, potentially leading to remote code execution. Installations
that used Redis' ACL system to restrict hyperloglog "HLL" commands are
unaffected by this issue. (Closes: #1108975)
* CVE-2025-48367: An unauthenticated connection could have caused repeated IP
protocol errors, leading to client starvation and ultimately become a
Denial of Service (DoS) attack. (Closes: #1108981)
redis (5:8.0.2-1) unstable; urgency=medium
* New upstream security release:
- CVE-2025-27151: Fix an stack-based buffer overflow in redis-check-aof
caused by the use of memcpy with strlen(filepath) when copying a
user-supplied file path into a fixed-size stack buffer. This allowed an
attacker to overflow the stack and potentially achieve arbitrary code
execution. (Closes: #1106822)
* Update debian/watch to consider 8.x versions again after the recent
licensing change.
-- Chris Lamb <[email protected]> Fri, 30 May 2025 12:05:58 -0700
The full debdiff is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] / chris-lamb.co.uk
`-
Please consider pre-approval for redis 5:8.0.2-2
Please go ahead and remove the moreinfo tag once the package is
available in unstable.
The test fails with LOLWUT in the error message and I also
see LOLWUT improvements mentioned in the redis diff. Is this unintended behavior change?
I do regularly wonder how smart tests like these are, to check for some magic string in an output. A change like this shouldn't cause issues.
I've also prepared another upload (5:8.0.2-3) that simply includes this
change (debdiff attached),
But yes, let's do this now to resolve it. But I'd not push to hard on upstream to put this back, instead python-redis could improve their
testing instead. But I'll leave that to you.
https://debusine.debian.net/debian/developers/work-request/120838/
The errors here are for gitlab and php-horde-hashtable (bad
dependencies), and proftpd-dfsg fails too, although outside of any
Redis-related tests.
The failure in debusine's autopkgtest is a bit opaque to me, can it be retried on the debusine infrastructure to check if it's flaky?
On 15-07-2025 19:17, Chris Lamb wrote:
The failure in debusine's autopkgtest is a bit opaque to me, can it be >>>retried on the debusine infrastructure to check if it's flaky?
Retrying these tests now… okay, no change in the results. Wish we
had 'reference' tests on Debusine like we do on the Freexian CI!
Seeing this is a permission issue, is debusine's autopkgtest always
failing on debusine infrastructure? I assume so. As the release date
is getting close, can we have the upload please?
On Thu, Jul 17, 2025 at 01:33:12PM +0200, Paul Gevers wrote:
Seeing this is a permission issue, is debusine's autopkgtest always
failing on debusine infrastructure? I assume so. As the release date
is getting close, can we have the upload please?
It's likely because of insufficient isolation of some kind, since
those test cases require either a privileged container or a VM, and
Debusine doesn't necessarily pick the right defaults for that sort of
thing at the moment. It should work on ci.debian.net, so please just
ignore this failure for now.
Retrying these tests now… okay, no change in the results. Wish we
had 'reference' tests on Debusine like we do on the Freexian CI!
Seeing this is a permission issue, is debusine's autopkgtest always >>failing on debusine infrastructure? I assume so. As the release date
is getting close, can we have the upload please?
It's likely because of insufficient isolation of some kind, since those
test cases require either a privileged container or a VM, and Debusine doesn't necessarily pick the right defaults for that sort of thing at
the moment. It should work on ci.debian.net, so please just ignore this failure for now.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 41:59:06 |
| Calls: | 12,109 |
| Files: | 15,006 |
| Messages: | 6,518,416 |