Critical NGINX Security Update - Update Your 3CX Now

Time wrong on the phone will also do this.
Yes I checked this first trying to link 2FA from WiFi and then from 4G but this wasa failure.
 
Thanks for the clarification. I have at leas one system that has reported update installation yesterday but is still on 6.1.0-52-amd64 without a reboot. Uptime is 18 days.
It seems you're even further behind than just the latest kernel update. Before 6.1.0-56-amd64 was released, you should already have been running 6.1.0-54-amd64, but you're still on 6.1.0-52-amd64.

There could be several reasons for this. GRUB might be configured to boot an older kernel, the kernel updates might not be getting installed, or the expected reboot might not be occurring.

Since you mentioned that the system reported update installation, I'll assume automatic updates are enabled and the update was not performed manually, which in thise case it should also install Debian security updates and reboot if required.
If this is the case, could you also confirm that you're running Update 1801 and that under Admin → System → Updates, there are no Debian OS security updates available?

You can also run a few checks via SSH to help narrow down the cause:

sudo apt update
apt policy linux-image-amd64
dpkg -l 'linux-image-6.1.0-*'
grep -E '^GRUB_(DEFAULT|SAVEDEFAULT)=' /etc/default/grub
ls -l /run/reboot-required

These should help you check for APT repository errors, whether the latest kernel is available or installed, whether a reboot is pending, and whether GRUB is configured to boot an older kernel.

Feel free to send me a PM with the results or contact our support team if you'd like to look into this further, as it's a bit outside the scope of this thread, given that your PBX has already been updated to Update 20.0.10.1801, which addresses the NGINX vulnerability being discussed here.
 

Forum statistics

Threads
112,562
Messages
593,315
Members
165,780
Latest member
youwillbrun