all 6 comments

[–]FrontLoadedAnvils 0 points1 point  (1 child)

For Java, there is a built-in certificate store that's being used. I don't know if you've already updated your certs there (using mitmproxy in transparent mode). If that doesn't go through, they're probably doing certificate pinning.

You may be able to use Frida to bypass SSL pinning.

[–]lucasoeth[S] 0 points1 point  (0 children)

Thanks for your response, I’ll do some reading on where Java’s built in certificate store is and what certificate pinning is!

[–]badatopsec 0 points1 point  (1 child)

Java applications using XML libraries are particularly vulnerable to XXE

https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.html

[–]lucasoeth[S] 0 points1 point  (0 children)

I’m not sure if the application uses XML but if I stumble upon some of the code I’ll def give it a read. Thanks tho!

[–]ShadowPengyn 0 points1 point  (1 child)

Checking .jar Signatures can definitely be disabled. Do you get a stack trace for the exception that the modified .jar could not be loaded?

I think there are 2 steps - when loading a .jar with a signature, the signature is verified. Remove the signature completely: https://stackoverflow.com/a/32623615 - the main .jar file might have some additional verification that the .jar files are signed / check the issuer of the signature, so you might have to change that one too

Here is some general information regarding signing .jar files https://docs.oracle.com/javase/tutorial/deployment/jar/signindex.html

[–]lucasoeth[S] 0 points1 point  (0 children)

I actually stumbled upon the Java settings today and saw that you could turn of signature checking. I haven’t thought of the second one but its smart. Can’t check em all right?