[JBoss JIRA] Closed: (JBAS-3861) DeploymentFileRepository can be used to write/remove arbitrary files in the filesystem
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3861?page=all ]
Dimitris Andreadis closed JBAS-3861.
------------------------------------
Resolution: Done
Fixed in all branches (3.2.x, 4.0.x, 4.2.x, HEAD).
> DeploymentFileRepository can be used to write/remove arbitrary files in the filesystem
> --------------------------------------------------------------------------------------
>
> Key: JBAS-3861
> URL: http://jira.jboss.com/jira/browse/JBAS-3861
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Management services
> Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1, JBossAS-3.2.8 Final, JBossAS-4.0.3 Final, JBossAS-4.0.2 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.0 Final, JBossAS-3.2.5 Final
> Reporter: Dimitris Andreadis
> Assigned To: Dimitris Andreadis
> Priority: Critical
> Fix For: JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 , JBossAS-3.2.8.SP2, JBossAS-5.0.0.Beta1
>
>
> Symantec discovered a flaw in the DeploymentFileRepository
> class of the JBoss application server. A remote attacker who
> is able to access the console manager could read or write to
> files with the permissions of the JBoss user. This could
> potentially lead to arbitrary code execution as the JBoss
> user. (CVE-2006-5750)
> Please note that the JBoss console manager should always be
> secured prior to deployment. By default, the JBoss installer
> gives users the ability to password protect the console
> manager, limiting an attack using this vulnerability to
> authorised users. These steps can also be performed manually.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss
> This vulnerability afffects all JBoss releases from v3.2.4 to v.4.0.5
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBAS-3861) DeploymentFileRepository can be used to write/remove arbitrary files in the filesystem
by Ryan Campbell (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3861?page=all ]
Ryan Campbell updated JBAS-3861:
--------------------------------
Security: Public (was: JBoss Internal)
> DeploymentFileRepository can be used to write/remove arbitrary files in the filesystem
> --------------------------------------------------------------------------------------
>
> Key: JBAS-3861
> URL: http://jira.jboss.com/jira/browse/JBAS-3861
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Management services
> Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1, JBossAS-3.2.8 Final, JBossAS-4.0.3 Final, JBossAS-4.0.2 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.0 Final, JBossAS-3.2.5 Final
> Reporter: Dimitris Andreadis
> Assigned To: Dimitris Andreadis
> Priority: Critical
> Fix For: JBossAS-4.0.5.SP1 , JBossAS-5.0.0.Beta1, JBossAS-4.2.0.CR1, JBossAS-3.2.8.SP2
>
>
> Symantec discovered a flaw in the DeploymentFileRepository
> class of the JBoss application server. A remote attacker who
> is able to access the console manager could read or write to
> files with the permissions of the JBoss user. This could
> potentially lead to arbitrary code execution as the JBoss
> user. (CVE-2006-5750)
> Please note that the JBoss console manager should always be
> secured prior to deployment. By default, the JBoss installer
> gives users the ability to password protect the console
> manager, limiting an attack using this vulnerability to
> authorised users. These steps can also be performed manually.
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SecureJBoss
> This vulnerability afffects all JBoss releases from v3.2.4 to v.4.0.5
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3879) org.jboss.resource.adapter.jdbc.WrappedConnection does not handle early rollbacks properly
by David Kilzer (JIRA)
org.jboss.resource.adapter.jdbc.WrappedConnection does not handle early rollbacks properly
------------------------------------------------------------------------------------------
Key: JBAS-3879
URL: http://jira.jboss.com/jira/browse/JBAS-3879
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management services
Affects Versions: JBossAS-4.0.2 Final
Environment: Microsoft Windows XP [Version 5.1.2600]
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode)
jTDS-1.2.0
MS SQL Server 2000 SP4 (separate server running WIndows 2003 Server)
Reporter: David Kilzer
Assigned To: Dimitris Andreadis
When an "early" rollback is performed (see code example below) using a java.sql.Connection from a JBossAS-managed DataSource, the following stack trace is produced:
java.sql.SQLException: rollback() should not be called while in auto-commit mode.
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.rollback(ConnectionJDBC2.java:1989)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.jdbcRollback(BaseWrapperManagedConnection.java:535)
at org.jboss.resource.adapter.jdbc.WrappedConnection.rollback(WrappedConnection.java:460)
at package.MyClass.testWrappedConnectionBehavior(MyClass.java:71)
[...]
However, when this same code is run without using a JBossAS-managed DataSource, it works with no SQLException being thrown:
private void testWrappedConnectionBehavior(DataSource dataSource) {
Connection connection = null;
try {
connection = dataSource.getConnection();
connection.setAutoCommit(false);
connection.rollback();
}
catch (SQLException e) {
e.printStackTrace(System.err);
}
finally {
if (connection != null) {
try {
connection.close();
}
catch (SQLException ignored) {
}
}
}
}
The org.jboss.resource.adapter.jdbc.WrappedConnection class should be able to handle an early rollback properly.
This issue originally filed with Spring: http://opensource.atlassian.com/projects/spring/browse/SPR-2862
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months