Vulnerability Details : CVE-2007-1036
The default configuration of JBoss does not restrict access to the (1) console and (2) web management interfaces, which allows remote attackers to bypass authentication and gain administrative access via direct requests.
At least one public exploit which can be used to exploit this vulnerability exists!
Exploit prediction scoring system (EPSS) score for CVE-2007-1036
Probability of exploitation activity in the next 30 days: 97.09%
Percentile, the proportion of vulnerabilities that are scored at or less: ~ 100 % EPSS Score History EPSS FAQ
Metasploit modules for CVE-2007-1036
-
JBoss DeploymentFileRepository WAR Deployment (via JMXInvokerServlet)
Disclosure Date : 2007-02-20exploit/multi/http/jboss_invoke_deployThis module can be used to execute a payload on JBoss servers that have an exposed HTTPAdaptor's JMX Invoker exposed on the "JMXInvokerServlet". By invoking the methods provided by jboss.admin:DeploymentFileRepository a stager is deployed to finally upload the selected payload to the target. The DeploymentFileRepository methods are only available on Jboss 4.x and 5.x. Authors: - Patrick Hof - Jens Liebchen - h0ng10 -
JBoss JMX Console Deployer Upload and Execute
Disclosure Date : 2007-02-20exploit/multi/http/jboss_maindeployerThis module can be used to execute a payload on JBoss servers that have an exposed "jmx-console" application. The payload is put on the server by using the jboss.system:MainDeployer functionality. To accomplish this, a temporary HTTP server is created to serve a WAR archive containing our payload. This method will only work if the target server allows outbound connections to us. Authors: - jduck <[email protected]> - Patrick Hof - h0ng10
CVSS scores for CVE-2007-1036
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Source |
---|---|---|---|---|---|
7.5
|
HIGH | AV:N/AC:L/Au:N/C:P/I:P/A:P |
10.0
|
6.4
|
[email protected] |
CWE ids for CVE-2007-1036
-
Assigned by: [email protected] (Primary)
Vendor statements for CVE-2007-1036
-
Red Hat 2007-05-18The JBoss AS console manager should always be secured prior to deployment, as directed in the JBoss Application Server Guide and release notes. By default, the JBoss AS installer gives users the ability to password protect the console manager. If the user did not use the installer, the raw JBoss services will be in a completely unconfigured state and these steps should be performed manually: http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss
-
http://www.securityfocus.com/archive/1/460605/100/0/threaded
-
http://www.securitytracker.com/id?1017677
-
http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureTheJmxConsole
-
http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss
-
https://exchange.xforce.ibmcloud.com/vulnerabilities/32596
-
http://www.kb.cert.org/vuls/id/632656
US Government Resource
-
http://www.securityfocus.com/archive/1/460597/100/0/threaded
-
http://www.securityfocus.com/archive/1/460695/100/0/threaded
- cpe:2.3:a:jboss:jboss_application_server:*:*:*:*:*:*:*:*