CVE-2026-56452
Description
A flaw was found in the sshd-scp component of Apache MINA SSHD, a Java library for client-side and server-side SSH. The implementation for receiving files or directories via Secure Copy Protocol (SCP) did not properly validate filenames. A remote attacker could exploit this by sending specially crafted filenames containing path traversal sequences, leading to files being written to arbitrary locations on the system. This could result in unauthorized modification of system files or data.
Statement
Red Hat Product Security has determined that this vulnerability does not affect any currently supported Red Hat product. This assessment may evolve based on further analysis and discovery. For more information about this vulnerability and the products it affects, please see the linked references.
Mitigation
To mitigate this issue, restrict network access to services that use Apache MINA SSHD's `sshd-scp` component for receiving files, ensuring only trusted clients can connect. If SCP file reception is not a required feature, consider disabling it within the application's configuration to prevent exploitation. Consult the application's documentation for specific instructions on how to configure or disable SCP functionality.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
