Keywords: Drupal - AWS - How to - Upgrade
It looks there is a fix for this issue in release Drupal Version 7.65-1.
Currently I have many virtual machines in AWS which have Bitnami Drupal 7.61-1 stack.
Should they be updated?
Which are my other options to fix this security hole than creating a new Bitnami 7.65-1 instance and move my application there?
I have run these commands on my 7.61-1 debian instance:
1. sudo apt-get update
2. sudo unattended-upgrade --dry-run -d
(gave: No packages found that can be upgraded unattended and no pending auto-removals)
3. sudo apt-get upgrade
The following packages will be upgraded:
base-files gnupg gnupg-agent gpgv libc-bin libc-dev-bin libc-l10n libc6 libc6-dev libxapian30 linux-image-4.9.0-8-amd64
linux-libc-dev locales locales-all multiarch-support tzdata
4. sudo apt-get dist-upgrade (0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.)
- httpd -v shows instance has Apache/2.4.37
So the apache did not update like this, I do not have much more experience so is it possible to fix this issue like this?