CVE-2017-20284
Description
A flaw was found in Resin. This vulnerability, located in the documentation web application (resin-doc), allows unauthorized remote attackers to access and read sensitive files on the system. By manipulating a specific input parameter, attackers can bypass security restrictions and read files outside of their intended directory, leading to unauthorized information disclosure.
Statement
An IMPORTANT severity path traversal vulnerability (CWE-22) was found in the Caucho Resin documentation web application (resin-doc). No Red Hat products are currently listed as affected by this flaw. A remote, unauthenticated attacker can send specially crafted requests containing directory traversal sequences via the inputFile request parameter of the jndi-appconfig tutorial servlet, allowing files outside the intended tutorial directory on the underlying system to be read, resulting in unauthorized information disclosure of sensitive data. Red Hat rates this flaw with a CVSS 3.1 base score of 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N); the CVE record also carries a CVSS 4.0 score of 8.7, but both reflect the same network-exploitable, unauthenticated issue with high confidentiality impact and no impact to integrity or availability. Exploitation of this issue has been observed in the wild, with evidence first reported by the Shadowserver Foundation on 2021-12-10.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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 to 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.
