Hmmm ... its not clear what exploit is used (from just reading the file at the
URL you gave).
The RPM versions (4.1/4.2) mentioned in the URL are quite ancient (circa RHL
8/9).
Even on those ancient systems, /var/lib/rpm requires access to root:root (or
rpm:rpm) in order to modify an rpmdb (but the derivative task of the exploit is
hiding a rootkit, where root:root has already been achieved, by changing
information in the rpmdb).
The provision in RPM for careful rootkit forensics is to use "rpm -Vp ..." from
a CDROM (or other offline/immutable media).
Hardening the manifest of installed packages (i.e. what is in an rpmdb) on an
already exploited system would require a security protocol to
authenticate/authorize rpm installations, most likely using a TPM and a trusted
boot to ensure that the RPM executable was not compromised, and then to keep
track of the list of package headers which SHOULD be installed, as well as
verifying header signatures before verifying package contents.
This isn't an easy problem to solve.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/196#issuecomment-292833133
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
