qtc-de
commented
1 year ago Hi Nicolas,
thanks for reporting :+1:
Have you any further information that could clarify why the certificate is bad? As far as I can tell, the error shows up when rmg attempts to connect to the actual RMI endpoint. The registry itself is not TLS protected (this is the reason why the general enumeration works without any problems). However, the RMI endpoint bound to the registry is, as one can see from the following output:
[+] - HPDM Server RMI
[+] --> com.hp.hpdm.interf.ServiceInterf (unknown class)
[+] Endpoint: system:40002 TLS: yes ObjID: [-52a5d3ef:18782b753bf:-7fff, 2349307879934226592]Unfortunately, the provided stack trace gives no indicator why the TLS certificate was considered bad. The output of something like openssl s_client -connect system 40002 could help to clarify this.
rmg generally treats all TLS certificates as trusted, but a similar issue was also reported for beanshooter some time ago. In this issue, the error message was more clear an indicated that the certificate algorithm was no longer supported. I expect a similar reason for your issue. Looking at the SSLTransport.decode method that throws the exception, one finds statements like the following:
} catch (UnsupportedOperationException unsoe) { // SSLv2Hello
// Code to deliver SSLv2 error message for SSL/TLS connections.
if (!context.sslContext.isDTLS()) {
context.outputRecord.encodeV2NoCipher();
if (SSLLogger.isOn && SSLLogger.isOn("ssl")) {
SSLLogger.finest("may be talking to SSLv2");
}
}
throw context.fatal(Alert.UNEXPECTED_MESSAGE, unsoe);So it is likely that your exception is also raised because the certificate or other TLS parameters do not match your minimal required policies. However, without knowing the certificate details, it is hard to tell :shrug:
Best, Tobias
dinosn
Hello,
One more issue if there is time to resolve :)
The request seem to failing with an alert for bad_certificate
Enum is able to retrieve information,
Thank you for the great work!
Regards, Nicolas