Authenticated code execution via JSP filename misclassification
Published Feb 4, 2020 · Updated Sep 16, 2024
Command execution in IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 allows remote authenticated users to execute JSP content. Under specialized conditions, the server misinterprets a maliciously crafted filename as JSP content and executes it; IBM has not identified the responsible file-creation path. Successful exploitation requires authenticated access and those specialized conditions, and grants code execution with the application server process's access.
Summary
What happened
Command execution in IBM WebSphere Application Server 7.0, 8.0, 8.5, and 9.0 allows remote authenticated users to execute JSP content. Under specialized conditions, the server misinterprets a maliciously crafted filename as JSP content and executes it; IBM has not identified the responsible file-creation path. Successful exploitation requires authenticated access and those specialized conditions, and grants code execution with the application server process's access.
The record
- CVE
- CVE-2020-4163
- Published
- Feb 4, 2020
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM WebSphere Application Server
- Classifications
- T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 4, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.0
- Affected versionversion=8.0
- Affected versionversion=8.5
- Affected versionversion=9.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo