The JSch StrictHostKeyChecking configuration is set to no, this indicates that connections may be made to unknown servers or servers that have changed their keys, generating new ones and adding them by default to the known server files.
- Start connections to untrusted servers.
- Increase the possibility of attacks such as MitM and spoofing.
- Receive or send malicious data or files.
- Leak sensitive information such as users and passwords.
- Limit access to administrative services such as SSH.
- Implement safe values for StricktHostKeyChecking configuration.
Anonymous attacker from the Internet.
⌚ 15 minutes.
Default score using CVSS 3.1. It may change depending on the context of the src.
Default score using CVSS 4.0. It may change depending on the context of the src.
The application enables Strict Host Key Checking
java.util.Properties config = new java.util.Properties();
config.put("StrictHostKeyChecking", "yes");
session.setConfig(config);
The application does not enable Strict Host Key Checking
java.util.Properties config = new java.util.Properties();
config.put("StrictHostKeyChecking", "no");
session.setConfig(config);