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] [Resolved] (DERBY-6619) After silently swallowing SecurityExceptions, Derby can leak class loaders
Date Mon, 25 Aug 2014 18:01:03 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dag H. Wanvik resolved DERBY-6619.

    Resolution: Fixed

Resolving the issue again after the second set of changes, also backported to 10.11.

> 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
>             Fix For:,
>         Attachments: derby-6619-2-refinement.diff, derby-6619-2.diff, derby-6619-2b.diff,
derby-6619.diff, derby-6619.status, derby-6619b.diff, derby-6619c.diff, derby.log, system-loader.diff
> 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

View raw message