Linux error while loading shared libraries invalid elf header

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help: «Error while loading shared binaries» — «Invalid ELF Header» after Windows Defender threat #4745

Help: «Error while loading shared binaries» — «Invalid ELF Header» after Windows Defender threat #4745

Comments

I was simply running ranger on my Debian WSL setup, when Windows Defender alterted me of what it thought was a Trojan

From the fact that the file’s in the WSL program directory, and it happened right after I ran a command, I assumed it could be a false alarm, but I couldn’t be too sure so I simply quarantined it.

However, now every time I run apt, I get this error:
apt-get: error while loading shared libraries: /lib/x86_64-linux-gnu/libbz2.so.1.0: invalid ELF header

I do assume that the ELF header issue is because of Windows Defender, but I’m not sure whether this is actually a threat or just a false alarm or not, some clarification and/or investigation would be appreciated.

The text was updated successfully, but these errors were encountered:

Источник

Arch Linux

Hi list,
since two or three system updates I frequently receive ‘invalid ELF header ‘ warnings when using pacman, but they don’t really caused errors. Now, trying to install mplayer, I get an error:

error while loading shared library /usr/lib/libsmbclient.so.0: invalid ELF header

There are some reports in Ubuntu forums about this, but searching the arch forum no yielded results. Whats that all about the ELF headers and how to remedy the problem?

Last edited by 4on6 (2012-02-15 23:01:15)

#2 2012-02-15 19:17:08

Re: [SOLVED] Invalid ELF header

Have you tried reinstalling smbclient? Maybe it got corrupted.
Is your system up to date?

#3 2012-02-15 19:38:38

Re: [SOLVED] Invalid ELF header

Have you tried reinstalling smbclient? Maybe it got corrupted.
Is your system up to date?

I just updated a few minutes ago. Reinstalling did not work, pacman complains there are about 30 conflicts (files exist in filesystem)

#4 2012-02-15 19:46:33

Re: [SOLVED] Invalid ELF header

Have you tried resolving the ‘file exist in filesystem’ issue: https://bbs.archlinux.org/viewtopic.php?id=130138 ?

#5 2012-02-15 20:32:10

Re: [SOLVED] Invalid ELF header

Have you tried resolving the ‘file exist in filesystem’ issue: https://bbs.archlinux.org/viewtopic.php?id=130138 ?

Not yet, its quite a lot of work. I’m half through the list, and they are all false alarms it seems.

(1/1) Prüfe auf Dateikonflikte [################################################] 100% Fehler: Konnte den Vorgang nicht durchführen (In Konflikt stehende Dateien) smbclient: /usr/bin/net existiert im Dateisystem smbclient: /usr/bin/nmblookup existiert im Dateisystem smbclient: /usr/bin/rpcclient existiert im Dateisystem smbclient: /usr/bin/smbcacls existiert im Dateisystem smbclient: /usr/bin/smbclient existiert im Dateisystem smbclient: /usr/bin/smbcquotas existiert im Dateisystem smbclient: /usr/bin/smbget existiert im Dateisystem smbclient: /usr/bin/smbspool existiert im Dateisystem smbclient: /usr/bin/smbtar existiert im Dateisystem smbclient: /usr/bin/smbtree existiert im Dateisystem smbclient: /usr/include/libsmbclient.h existiert im Dateisystem smbclient: /usr/include/netapi.h existiert im Dateisystem smbclient: /usr/lib/cups/backend/smb existiert im Dateisystem smbclient: /usr/lib/libnetapi.so existiert im Dateisystem smbclient: /usr/lib/libnetapi.so.0 existiert im Dateisystem smbclient: /usr/lib/libsmbclient.so existiert im Dateisystem smbclient: /usr/lib/libsmbclient.so.0 existiert im Dateisystem smbclient: /usr/lib/libwbclient.so existiert im Dateisystem smbclient: /usr/lib/libwbclient.so.0 existiert im Dateisystem smbclient: /usr/share/man/man1/nmblookup.1.gz existiert im Dateisystem smbclient: /usr/share/man/man1/rpcclient.1.gz existiert im Dateisystem smbclient: /usr/share/man/man1/smbcacls.1.gz existiert im Dateisystem smbclient: /usr/share/man/man1/smbclient.1.gz existiert im Dateisystem smbclient: /usr/share/man/man1/smbcquotas.1.gz existiert im Dateisystem smbclient: /usr/share/man/man1/smbget.1.gz existiert im Dateisystem smbclient: /usr/share/man/man1/smbtar.1.gz existiert im Dateisystem smbclient: /usr/share/man/man1/smbtree.1.gz existiert im Dateisystem smbclient: /usr/share/man/man7/libsmbclient.7.gz existiert im Dateisystem Fehler sind aufgetreten, keine Pakete wurden aktualisiert. [tj@arch ~]$ sudo pacman -Qo /usr/bin/net Fehler: Kein Paket besitzt /usr/bin/net [tj@arch ~]$ sudo pacman -Qo /usr/bin/nmblookup Fehler: Kein Paket besitzt /usr/bin/nmblookup [tj@arch ~]$ sudo pacman -Qo /usr/bin/rpcclient Fehler: Kein Paket besitzt /usr/bin/rpcclient [tj@arch ~]$ sudo pacman -Qo /usr/bin/smbcacls Fehler: Kein Paket besitzt /usr/bin/smbcacls [tj@arch ~]$ sudo pacman -Qo /usr/bin/smbcquotas Fehler: Kein Paket besitzt /usr/bin/smbcquotas [tj@arch ~]$ sudo pacman -Qo /usr/bin/smbget Fehler: Kein Paket besitzt /usr/bin/smbget [tj@arch ~]$ sudo pacman -Qo /usr/bin/smbspool Fehler: Kein Paket besitzt /usr/bin/smbspool [tj@arch ~]$ sudo pacman -Qo /usr/bin/smbtar Fehler: Kein Paket besitzt /usr/bin/smbtar [tj@arch ~]$ sudo pacman -Qo /usr/include/libsmbclient.h Fehler: Kein Paket besitzt /usr/include/libsmbclient.h [tj@arch ~]$ sudo pacman -Qo /usr/include/netapi.h Fehler: Kein Paket besitzt /usr/include/netapi.h [tj@arch ~]$ sudo pacman -Qo /usr/include/netapi.h 

#6 2012-02-15 20:40:00

Re: [SOLVED] Invalid ELF header

These files are provided by smbclient. Have you installed smbclient from the repos or some other way?

[karol@black ~]$ nosr /usr/bin/smbcacls extra/smbclient [karol@black ~]$ nosr /usr/include/netapi.h extra/smbclient

Last edited by karol (2012-02-15 20:41:57)

#7 2012-02-15 20:46:37

Re: [SOLVED] Invalid ELF header

These files are provided by smbclient. Have you installed smbclient from the repos or some other way?

[karol@black ~]$ nosr /usr/bin/smbcacls extra/smbclient [karol@black ~]$ nosr /usr/include/netapi.h extra/smbclient

I did not actively install smbclient, must habe been some kind of dependency.
Can’t install ‘nosr’.

[tj@arch ~]$ sudo pacman -Qo 'which smbclient' Fehler: Konnte 'which smbclient' in PATH nicht finden: Datei oder Verzeichnis nicht gefunden [tj@arch ~]$ sudo pacman -Qo 'which libsmbclient' Fehler: Konnte 'which libsmbclient' in PATH nicht finden: Datei oder Verzeichnis nicht gefunden [tj@arch ~]$ nosr /usr/bin/smbcacls bash: nosr: Kommando nicht gefunden. [tj@arch ~]$ sudo pacman -Ss nosr [tj@arch ~]$ sudo pacman -Qo 'which smbcacls' Fehler: Konnte 'which smbcacls' in PATH nicht finden: Datei oder Verzeichnis nicht gefunden

Источник

rpm: error while loading shared libraries: invalid ELF header

In this instance, either liblzma.so or the link to it (/usr/lib64/liblzma.so.0) had gotten overwritten.

$ rpm -qa | grep binutils rpm: error while loading shared libraries: /usr/lib64/liblzma.so.0: invalid ELF header

To resolve this issue, the liblzma.so file and associated soft link need to be restored. Follow the steps outlined below in order to restore the .so file and associated soft links.

1. Ensure that the softlink /usr/lib64/liblzma.so.0 exists and points to liblzma.so.0.0.0.

# ls -l /usr/lib64/liblzma.so.0 lrwxrwxrwx 1 root root 16 Mar 31 15:42 /usr/lib64/liblzma.so.0 -> liblzma.so.0.0.0

# file /usr/lib64/liblzma.so.0.0.0 ./usr/lib64/liblzma.so.0.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped

2. If the softlink does not exist try the following:

– Try to use yum to reinstall the xz-libs. However, if rpm is having a problem, yum likely will too.

3. If that does not work, unpack the rpm and copy the new shared library file over the invalid file. As rpm is having trouble, unpacking the rpm will likely need to be done on a different system.

– Download the appropriate xz-libx rpm from the source respository and use the rpm2cpio and cpio commands to unpack the rpm.

# rpm2cpio xz-libs-4.999.9-0.5.beta.20091007git.el6.x86_64.rpm | cpio -idv ./usr/lib64/liblzma.so.0 ./usr/lib64/liblzma.so.0.0.0 ./usr/share/doc/xz-libs-4.999.9 ./usr/share/doc/xz-libs-4.999.9/COPYING.GPLv2 ./usr/share/doc/xz-libs-4.999.9/COPYING.GPLv3 ./usr/share/doc/xz-libs-4.999.9/COPYING.LGPLv2.1 421 blocks

4. Copy the liblzma.so.0.0.0 from the unpacked rpm over the existing shared library file:

# cp -pv ./usr/lib64/liblzma.so.0.0.0 /usr/lib64/liblzma.so.0.0.0 cp: overwrite '/usr/lib64/liblzma.so.0.0.0'? y './usr/lib64/liblzma.so.0.0.0' -> '/usr/lib64/liblzma.so.0.0.0'

# file /usr/lib64/liblzma.so.0.0.0 /usr/lib64/liblzma.so.0.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped

5. Test that rpm works as expected.

# rpm -qf /usr/lib64/liblzma.so.0.0.0 xz-libs-4.999.9-0.5.beta.20091007git.el6.x86_64

Источник