RageLtMan 074120a2d3 Scaffold HTTP Header Injection Exploit
Using the infrastructure developped for use in the log4shell HTTP
scanner, implement a basic HTTP exploit module which performs the
same action as the scanner does per-host on a specific target; but
instead of logging the vulnerability, return a crafted LDAP search
response containing the payload encoded within the search response.

The crux of this effort lies in payload generation, specifically in
crafting the legal LDAP response packet out of the request data and
generated JAR-format payload. The payload selection is based on an
offline discussion with @Mihi during which he indicated JNDI's
ability to load JARs in the same way as raw Java classes. This
assumption/interpretation on my part may be incorrect.

At present, the delivered LDAP search response appears to be valid
in WireShark, and the vulnerable test docker is showing internal
values in its console output a la:
```
Received a request for API version com.sun.jndi.ldap.LdapCtx@3575a
```
which shows that it is processing the response on its end, just
not in the way we would prefer, yet.

This may be a result of how the MSF payload is being shuffled and
mutated by the packet construction method, or a mistake in the way
i pass in the queried base DN or execute the LDAP search response
transaction.

Testing: fails currently for aforementioned reason

TODO:
  figure out how to encode the payload/LDAP response correctly
  continue testing until verified and upstreamed
2021-12-29 09:10:07 -05:00
2021-08-09 12:16:12 -05:00
2021-08-09 12:16:12 -05:00
2021-12-28 14:50:03 -05:00
2018-10-21 22:34:19 +02:00
2021-11-05 15:14:19 +00:00
2021-12-28 14:50:03 -05:00
2017-07-12 08:00:29 -05:00
2021-10-12 23:40:43 +01:00
2018-10-21 22:30:01 +02:00
2021-10-08 02:55:39 +05:30
2013-11-27 16:04:41 +10:00
2021-07-13 10:38:50 +01:00
2014-10-08 10:55:40 -05:00
2021-12-01 12:02:59 -06:00
2014-09-18 15:24:21 -05:00
2017-09-07 02:35:56 -05:00
2018-12-13 10:38:55 -06:00
2020-01-18 18:45:37 -06:00
2021-04-16 01:59:22 +01:00
2020-12-07 10:31:45 +00:00
2021-01-18 14:21:54 +00:00
2021-01-18 14:21:54 +00:00
2020-12-07 10:31:45 +00:00
2019-10-07 13:16:15 +05:30

Metasploit Build Status Maintainability Test Coverage Docker Pulls

The Metasploit Framework is released under a BSD-style license. See COPYING for more details.

The latest version of this software is available from: https://metasploit.com

Bug tracking and development information can be found at: https://github.com/rapid7/metasploit-framework

New bugs and feature requests should be directed to: https://r-7.co/MSF-BUGv1

API documentation for writing modules can be found at: https://rapid7.github.io/metasploit-framework/api

Questions and suggestions can be sent to: Freenode IRC channel or e-mail the metasploit-hackers mailing list

Installing

Generally, you should use the free installer, which contains all of the dependencies and will get you up and running with a few clicks. See the Dev Environment Setup if you'd like to deal with dependencies on your own.

Using Metasploit

Metasploit can do all sorts of things. The first thing you'll want to do is start msfconsole, but after that, you'll probably be best served by reading Metasploit Unleashed, the great community resources, or the wiki.

Contributing

See the Dev Environment Setup guide on GitHub, which will walk you through the whole process from installing all the dependencies, to cloning the repository, and finally to submitting a pull request. For slightly more information, see Contributing.

S
Description
Metasploit Framework
Readme Multiple Licenses 1.6 GiB
Languages
Ruby 95%
PowerShell 2.7%
C 1.2%
Python 0.4%
HTML 0.2%
Other 0.1%