Beyond
This is the beyond page that an additional post enumeration and assessment are conducted as the root user after compromising the target system; [[Blunder_Privilege_Escalation#[CVE-2019-14287](https //nvd.nist.gov/vuln/detail/CVE-2019-14287)|1]], [[Blunder_Privilege_Escalation_2#[CVE-2021-3156](https //nvd.nist.gov/vuln/detail/CVE-2021-3156)|2]], [[Blunder_Privilege_Escalation_3#[CVE-2021-3560](https //nvd.nist.gov/vuln/detail/CVE-2021-3560)|3]], [[Blunder_Privilege_Escalation_4#[CVE-2021-4034](https //nvd.nist.gov/vuln/detail/cve-2021-4034)|4]]
crontab
root@blunder:/root# crontab -l
# Edit this file to introduce tasks to be run by cron.
#
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
#
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').
#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
#
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
#
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h dom mon dow command
*/1 * * * * /root/reset.sh >> /root/log/root/reset.sh
root@blunder:/root# cat reset.sh
#!/bin/bash
ip=$(/usr/sbin/ifconfig ens160 | grep 'inet ' | awk '{print $2}')
sed -i "s%^.*url.*$%\"url\":\"http:\\\\/\\\\/$ip\\\\/\",%g" /var/www/bludit-3.9.2/bl-content/databases/site.php