-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE-2016-8735 - Remote Code Execution via JMX Ports #10893
Comments
/bounty $200 |
💎 $200 bounty • ProjectDiscovery Bounty Available for CVE Template ContributionSteps to Contribute:
Thank you for contributing to projectdiscovery/nuclei-templates and helping us democratize security!
Add a bounty • Share on socials
|
/attempt #10893
|
The bounty is up for grabs! Everyone is welcome to |
@ritikchaddha is java available to use as a code engine? |
/attempt #10893
|
/attempt #10893
|
💡 @hnd3884 submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
@yanisoln: Reminder that in 4 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
Is there an existing template for this?
Template requests
Description:
Apache Tomcat versions before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x before 9.0.0.M12 are vulnerable to remote code execution if JmxRemoteLifecycleListener is used and the JMX ports are exposed to attackers. The vulnerability exists due to inconsistent credential type handling, which was not aligned with the CVE-2016-3427 Oracle patch. Attackers with access to JMX ports can exploit this issue to execute arbitrary code remotely.
Severity: Critical
POC:
References:
Shodan Query:
html:"Apache Tomcat"
cpe:"cpe:2.3:a:apache:tomcat"
CPE:
cpe:2.3:a:apache:tomcat::::::::
cpe:2.3:a:apache:tomcat:9.0.0:-:::::::*
Anything else?
No response
The text was updated successfully, but these errors were encountered: