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] [Commented] (DERBY-6619) After silently swallowing SecurityExceptions, Derby can leak class loaders
Date Thu, 21 Aug 2014 16:09:13 GMT

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

Dag H. Wanvik commented on DERBY-6619:
--------------------------------------

I can see the following options:

- Keep the warning and just document it (Pro: avoid the issue
  being ignored, Con: noisy )

- Don't print the warning if the server is started from the command
  line (Pro: less nois, Con: added complexity and different engine
  behavior depending on start mode is somewhar undesirable in itself)

- Augment the default policy file with the needed permission if the
  server is started from the command line before loading it (Pro: less
  noisy, Con: complexity)

- Add the permission to the default policy (needs to be tightened up
  anyway as per our recommendation in the docs - it is already overly
  liberal) (Pro: simple, no noise, Con: less safe by default)



> 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: 10.11.1.2, 10.12.0.0
>
>         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