go-exploit
go-exploit copied to clipboard
vulncheck-oss
A Go-based Exploit Framework
Closes #234 Allows for protocols to have explicit flags that will resolve when they get defined. For example, if your exploit defines "HTTP" as it's protocol, this change automatically applies...
Part of #189 This is the first pass at adding a basic artifact storage to the framework. Changes are: - Add a SQL table for a really basic artifact set...
Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action
Adds a set off helper functions to help chain ASP.NET application state management functions. Historically, ASP.NET apps have been a bit of a nuisance to work with because of the...
This adds support for adding explicit payload support to an exploit. This provides a few things: - *Bring Your Own Payload* (BYOP). Long awaited ability to support user provided payloads....
Requires https://github.com/vulncheck-oss/go-exploit/pull/377 The goal is to put helper functions/wrappers in this package to reduce boilerplate and increase consistency. Also helps to prevent import cycle issues. Usage examples: ## Simple Version...
As discussed on our call, add a new payload "type" option that allows for the exploit author to specify what type of payload is supported by the exploit. This will...
This proposal is to replace the very large (and growing) pile of options for `protocol` with a [functional options](https://github.com/teivah/100-go-mistakes/blob/master/src/02-code-project-organization/11-functional-options/functional-options/main.go) pattern. I also propose that we adopt either the functional options...
Details: https://github.com/vulncheck-oss/go-exploit/pull/410#discussion_r2220000706
To prevent things like this: ``` time=2025-07-17T12:58:40.855-06:00 level=SUCCESS msg="The target appears to be a vulnerable version!" host=192.168.23.48 port=443 vulnerable=yes time=2025-07-17T12:58:40.855-06:00 level=STATUS msg="Running command/args: 'cmd' - '/c certutil.exe -urlcache -split -f...