This is about the redis version shipped by the icingadb-redis-server package.
If this project does not control this, please comment where can I reach whomever is packaging that, and close this issue.
The redis server version in icingadb-redis-server is 7.0.2.
Redis latest is now 7.0.5, with 7.0.4 and 7.0.5 being security releases.
To Reproduce
Use the Icinga repositories, install the icingadb-redis-server package.
For Ubuntu for instance we have
Describe the bug
This is about the redis version shipped by the icingadb-redis-server package. If this project does not control this, please comment where can I reach whomever is packaging that, and close this issue.
The redis server version in icingadb-redis-server is 7.0.2. Redis latest is now 7.0.5, with 7.0.4 and 7.0.5 being security releases.
To Reproduce
Use the Icinga repositories, install the icingadb-redis-server package. For Ubuntu for instance we have
apt-cache policy icingadb-redis-server
icingadb-redis-server: Installed: 7.0.2-1.focal Candidate: 7.0.2-1.focal Version table: *** 7.0.2-1.focal 500 500 https://packages.icinga.com/ubuntu icinga-focal/main amd64 Packages 100 /var/lib/dpkg/status
icingadb-redis-server --version
Redis server v=7.0.2 sha=00000000:0 malloc=jemalloc-5.2.1 bits=64 build=5745ab037f18df44
Expected behavior
The redis shipped via the icingadb-redis-server should be updated to include security fixes.
Your Environment
Include as many relevant details about the environment you experienced the problem in
Additional context
A workaround for me would be to disable the affected Redis commands in the redis configuration. A better solution would be an package update which upgrades to 7.0.5. Redis changelog: https://raw.githubusercontent.com/redis/redis/7.0/00-RELEASENOTES