Closed naomipasherr closed 5 months ago
Hi @naomipasherr, thanks for reporting this. Could you please provide more details (stack trace) about the crash in plain text?
how i can get stack trace in ubuntu?
how i can get stack trace in ubuntu?
I mean the full message of the panic message. (paste the text instead of screenshot)
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x81aafa]
goroutine 38 [running]: ktbs.dev/mubeng/internal/server.(Proxy).onRequest.func1() /app/internal/server/handler.go:45 +0x5a created by ktbs.dev/mubeng/internal/server.(Proxy).onRequest /app/internal/server/handler.go:44 +0x37d
Hi @naomipasherr, thanks for providing that information. May I know how you use the mubeng (like the command)?
Reopening this while waiting for your reply.
Closing this as I didn't get a follow-up.
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x81aafa]
mubeng works correctly when we use in sqlmap nuclei and etc.... BUT some tools like Acunetix, Appscan when use proxy server, mubeng crushes
I guess maybe some packet corrupt but mubeng not handle it. please follow screenshot
Screenshots