-
Notifications
You must be signed in to change notification settings - Fork 1.7k
DynELF libcdb feature requrests #983
New issue
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
Comments
Most of these are doable, with the exception of "Could we add a test to make sure that all the links are working?". There's no way to automate this externally, it'd have to be something done on the libcdb side. |
Sure, I should have filed that on the libcdb repo. |
Closed via #986 |
There are still a few things from the above list missing:
|
Good catch, thanks! |
The libc databases might be updated to include the searched version, so a request that failed once might work in the future. Refs Gallopsled#983
Don't do any requests if the libc currently in use on the system running the exploit matches already. This is a small short circuit optimization when the remote target uses the same libc as the local one. This looks at the libc loaded by the local shell binary. This appears more dynamic than hardcoding library paths. Refs Gallopsled#983
* Retry failed lookups after one week in libcdb The libc databases might be updated to include the searched version, so a request that failed once might work in the future. Refs #983 * Update CHANGELOG
* Match against local system libc first in libcdb Don't do any requests if the libc currently in use on the system running the exploit matches already. This is a small short circuit optimization when the remote target uses the same libc as the local one. This looks at the libc loaded by the local shell binary. This appears more dynamic than hardcoding library paths. Refs #983 * Update CHANGELOG * Handle missing SHELL envvar * Fix hash lookup
The last two open items from the list are implemented now. |
The text was updated successfully, but these errors were encountered: