Ramblings about Python, C#, security, cryptography, and more.
May 25, 2019 | SQL Injection vulnerability found in LDMS 10.0.1.168 Service Update 5 due to improper username sanitization.
A SQL injection vulnerability has been identified in the web API endpoint located at https://<coreserver>/landesk/managementsuite/core/provisioning.secure/ProvisioningSecure.asmx.
This vulnerability is present within the Provisioning.Secure.dll utilized by this API endpoint. If we decompile this DLL, the vulnerability can be clearly seen within 2 methods.
May 25, 2019 | Use of a hard-coded encryption key in LDMS 10.0.1.168 Service Update 5 may lead to full managed endpoint compromise
Multiple cryptographic vulnerabilities have been identified in the web API endpoint at http://<coreserver>/landesk/managementsuite/core/cmp.secure. These vulnerabilities compromise the at-rest security model of all data protected by this module, and could lead to unauthorized device decryption, credential disclosure, and full managed endpoint compromise.
This API endpoint is used for encryption of such sensitive information as filevault credentials, administrative override credentials, Windows credent…
May 25, 2019 | Open directories in LDMS 10.0.1.168 Service Update 5 may lead to information disclosure and arbitrary code execution
By design, multiple directories on the LDMS core server are wide-open and globally readable via HTTP. For example, see the following web locations available on an LDMS core server:
While this is by design, it is a major architectural oversight. This design played an instrumental role in the discovery of many of these vulnerabilities, and allows for information disclosure and arbitrary code execution when paired wit…
May 25, 2019 | Improper access control and open directories in LDMS 10.0.1.168 Service Update 5 may lead to disclosure of administrator passwords
During an imaging task, the LANDesk provisioning subsystem creates a copy of each injected file in the globally readable network share \\<coreserver>\ldlogon\provisioning\config. This share is created during the LANDesk Management Core Server installation process, and the installer automatically sets the permissions such that "Everyone" can read from this directory.
Once the imaging task is finished, the file copies are usually removed. However, if an imaging task fails, the files are stored…
May 25, 2019 | A vulnerable web API endpoint in LDMS 10.0.1.168 Service Update 5 allows arbitrary file upload, which may lead to arbitrary remote code execution
When a LANDesk managed endpoint is reporting inventory and patch level information to the core server, it leverages a web API endpoint found at https://<coreserver>/upl/async_upload.asp. This endpoint does not properly sanitize user-provided values, which allows for an attacker to both control the uploaded file extension and the uploaded file location.
As this is an ASP.NET web page, we can simply open the file in a text editor to see the vulnerable code. I opened it using Notepad++ to take a look.
May 25, 2019 | Multiple vulnerabilities of varying severity have been identified in LDMS 10.0.1.168 Service Update 5
May 29, 2019 | There's no sense in re-inventing the wheel. By analyzing the work of the brilliant minds who came before, we can expand on their efforts to build something that meets our requirements.
Not everyone who calls themselves a hacker understands how the tools they use actually work. Even less of those folks are capable of building their own functional toolkit. This is a recipe for failure. While it's possible to get pretty far using other people's tools, using only tools made by other people ensures you'll never be as good as someone who can build their own. How much more so if you don't take the time to actually understand how those tools really work.
In the interest of…
May 30, 2019 | Before you go ahead and build your own shell, let's walk through one I've already written. That way you can avoid the same pitfalls I had to contend with.
I have a really bad habit of making an entirely new toolkit any time I need a single tool. A while back, I needed a shell for a pentest I was working on, and I went ahead and followed my usual pattern. I threw out everything I'd ever written and started with a fresh approach to the problem. Ended up building a new shell and a bunch of pivot utilities custom designed for the particular target I was attacking. It turned out pretty well, although it still has some drawbacks. We'll be analyzing …