-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Add opentsdb_key_cmd_injection exploit module and docs #18350
Add opentsdb_key_cmd_injection exploit module and docs #18350
Conversation
Notes
|
Thanks for your pull request! Before this can be merged, we need the following documentation for your module: |
Tested with the suggested Docker container setup with OpenTSDB 2.4.1 💯 with inline run params :
I was also able to get repeated shells with no problems. |
If you (@ErikWynter) are fine with it, I'll get the docs sorted now and we can get this shipped 👍 |
Release NotesAdds a new module that exploits an unauthenticated command injection vulnerability in OpenTSDB through 2.4.1 resulting in root access. |
@sjanusz-r7 oh wow that was fast. Thanks for testing everything so quickly and for adding the docs!! |
About
This change adds an exploit module and docs for an unauthenticated command injection vulnerability in OpenTSDB through 2.4.1 (CVE-2023-36812/CVE-2023-25826).
Vulnerable Application
OpenTSDB through 2.4.1 is affected. The module has been tested against 2.4.1.
Installation Information
Manual installation (not recommended)
For a manual installation, you can follow the official installation instructions here. This can be annoying though, so I would recommend using docker instead.
Docker installation (recommended)
For version 2.4.0, you can use the vulnhub docker image and follow the installation instructions here. That image was created for CVE-2020-35476, an older vulnerability in OpenTSDB through 2.4.0.
For any other version, you could leverage the vulhub image for OpenTSDB 2.4.0 and edit it to install the version you want. I followed this approach for 2.4.1 and it worked great.
Dockerfile
anddocker-entrypoint.sh
files from here and store them in a dedicated directory.Dockerfile
, replace all instances for2.4.0
with your desired version, eg2.4.1
docker-entrypoint.sh
docker-compose.yml
file with the following contents:I used this file structure:
docker-compose.yml
file:Verification Steps
Start msfconsole
Options
TARGETURI
The base path to OpenTSDB. The default value is /.
Targets
Scenarios
OpenTSDB 2.4.1 - Linux target