Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A9F33110F7 for ; Mon, 7 Jul 2014 16:46:34 +0000 (UTC) Received: (qmail 49109 invoked by uid 500); 7 Jul 2014 16:46:34 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 49082 invoked by uid 500); 7 Jul 2014 16:46:34 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 49070 invoked by uid 99); 7 Jul 2014 16:46:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jul 2014 16:46:34 +0000 Date: Mon, 7 Jul 2014 16:46:34 +0000 (UTC) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6617) Silently swallowed SecurityExceptions may disable Derby features, including security features. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053837#comment-14053837 ] Dag H. Wanvik commented on DERBY-6617: -------------------------------------- - The occurrence in PBInitialize line 157 is ok, I think, since the method returns a false in that case which will fail the call to FileMonitor#initialize, which again make BaseMonitor#runWithState return early (line 248), aborting the boot. The "false" return is ignored in FileMonitor(), but that is only used for Monitor#getMonitorLite. > Silently swallowed SecurityExceptions may disable Derby features, including security features. > ---------------------------------------------------------------------------------------------- > > Key: DERBY-6617 > URL: https://issues.apache.org/jira/browse/DERBY-6617 > Project: Derby > Issue Type: Bug > Components: Services > Affects Versions: 10.11.0.0 > Reporter: Rick Hillegas > > When the Monitor tries to read Derby properties, it silently swallows SecurityExceptions. This means that the properties will be silently ignored if Derby has not been granted sufficient privileges. This means that if you make a mistake crafting your security policy, then you may disable authentication and authorization. You may not realize this until you have incurred a security breach. This swallowing occurs at the following code locations: > {noformat} > org.apache.derby.impl.services.monitor.BaseMonitor readApplicationProperties Catch java.lang.SecurityException 1 line 1360 > org.apache.derby.impl.services.monitor.BaseMonitor runWithState Catch java.lang.SecurityException 0 line 280 > org.apache.derby.impl.services.monitor.FileMonitor PBgetJVMProperty Catch java.lang.SecurityException 1 line 183 > org.apache.derby.impl.services.monitor.FileMonitor PBinitialize Catch java.lang.SecurityException 1 line 120 > {noformat} > SecurityExceptions are swallowed at other locations in the Monitor. The implications of these swallowings should be understood and, at a minimum, security problems should be fixed: > {noformat} > org.apache.derby.impl.services.monitor.FileMonitor PBinitialize Catch java.lang.SecurityException 1 line 157 > org.apache.derby.impl.services.monitor.FileMonitor createDaemonGroup Catch java.lang.SecurityException 1 line 89 > {noformat} -- This message was sent by Atlassian JIRA (v6.2#6252)