Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 18 Aug 2014 22:13:21 +0000 (UTC)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12721691.1403014420095.26902.1408400001686@arcas>
In-Reply-To: <JIRA.12721691.1403014420095@arcas>
References: <JIRA.12721691.1403014420095@arcas>
Subject: [jira] [Comment Edited] (DERBY-6619) After silently swallowing
 SecurityExceptions, Derby can leak class loaders
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101393#comment-14101393 ] 

Dag H. Wanvik edited comment on DERBY-6619 at 8/18/14 10:13 PM:
----------------------------------------------------------------

Uploading a patch [^derby-6619.diff] which prints warnings on derby.log.

For example, with this invocation:
{code}
java -jar jars/sane/derbyrun.jar server start
{code}
which uses the default security manager, the derby.log looks as in [^derby.log].


was (Author: dagw):
Uploading a patch [derby-6619.diff] which prints warnings on derby.log.

For example, with this invocation:
{code}
java -jar jars/sane/derbyrun.jar server start
{code}
which uses the default security manager, the derby.log looks as in [^derby.log].

> After silently swallowing SecurityExceptions, Derby can leak class loaders
> --------------------------------------------------------------------------
>
>                 Key: DERBY-6619
>                 URL: https://issues.apache.org/jira/browse/DERBY-6619
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>            Reporter: Rick Hillegas
>            Assignee: Dag H. Wanvik
>         Attachments: derby-6619.diff, derby-6619.status
>
>
> As part of the fix for DERBY-3745, Derby silently swallows security exceptions and leaks class loaders. This can give rise to denial-of-service attacks. At a minimum, Derby should report the swallowed exceptions so that the security policy can be corrected and the application can be hardened against this attack. The swallowing occurs at these locations:
> {noformat}
> org.apache.derby.impl.services.timer.SingletonTimerFactory run Catch java.lang.SecurityException 0 line 175
> org.apache.derby.impl.services.timer.SingletonTimerFactory run Catch java.lang.SecurityException 1 line 158
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.2#6252)