db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-6619) After silently swallowing SecurityExceptions, Derby can leak class loaders
Date Tue, 19 Aug 2014 19:49:19 GMT

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

Dag H. Wanvik edited comment on DERBY-6619 at 8/19/14 7:48 PM:
---------------------------------------------------------------

Attaching [^derby-6619c.diff]: Suggested commit log:
{quote}
Patch derby-6619 which prints warnings on derby.log if permissions are missing to get and
set the context class loader in SingletonTimerFactory (which can lead to classloader leak).
Also adds a test of this by checking derby.log in SecureServerTest.
{quote}
Running regressions. {color:green}[Update: passed]{color}


was (Author: dagw):
Attaching [^derby-6619c.diff]: Suggested commit log:
{quote}
Patch derby-6619 which prints warnings on derby.log if permissions are missing to get and
set the context class loader in SingletonTimerFactory (which can lead to classloader leak).
Also adds a test of this by checking derby.log in SecureServerTest.
{quote}
Running regressions.

> 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, derby-6619b.diff, derby-6619c.diff,
derby.log
>
>
> 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)

Mime
View raw message