DPI-1047: 32-bit Oracle Client library cannot be loaded: "libclntsh.so: cannot open shared object file: No such file or directory
kildonan5 opened this issue · 2 comments
Hello, I'm working on getting odat standalone up and running on a fresh Kali install.
Ive downloaded and unzipped the latest stand-alone zip (odat-linux-libc2.5-x86_64-v2.3.zip) and extracted it.
Running a scan with odat is successful, but attempting to connect to a database with the command;
./odat-libc2.5-i686 all -s [MY_TARGET_IP] -p 1521 -d acme -U SCOTT -P TIGER
results in;
[1] ([MY_TARGET_IP]:1521): Is it vulnerable to TNS poisoning (CVE-2012-1675)?
[+] The target is vulnerable to a remote TNS poisoning
[2] ([MY_TARGET_IP]:1521): Testing all modules on the acme SID with the SCOTT/TIGER account
[-] Impossible to connect to the remote database: `DPI-1047: 32-bit Oracle Client library cannot be loaded: "libclntsh.so: cannot open shared object file: No such file or directory". See https://oracle.github.io/odpi/doc/installation.html#linux for help`
21:15:15 CRITICAL -: Impossible to connect to the remote database: DPI-1047: 32-bit Oracle Client library cannot be loaded: "libclntsh.so: cannot open shared object file: No such file or directory". See https://oracle.github.io/odpi/doc/installation.html#linux for help
Looking up those errors seem to imply i need the oracle instant client, but I thought the point of the stand alone install was that we didnt need to install anything else. What am I missing?
Partially answering my own issue;
Using the previous standalone 32 bit version does not show this error, so thats a temporary work around.
Following the Oracle setup guide for Kali resolved the issue for the current version. https://github.com/rapid7/metasploit-framework/wiki/How-to-get-Oracle-Support-working-with-Kali-Linux . Now I'm getting an ORA-03134 but thats because the database im trying to connect to is old.
In the odat directory, you have to execute this following command for creating a symbolic link:
ln -s libclntsh.so.12.1 libclntsh.so
If you have another missing .so file, you have to create a symbolic link with "ln -s".