You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/09/29 18:43:33 UTC

[jira] [Updated] (DERBY-6636) The public api of BaseDataFileFactory may allow blackhats to assume elevated privileges.

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

Rick Hillegas updated DERBY-6636:
---------------------------------
    Attachment: derby-6636-01-aa-usederbyinternals.diff

Attaching derby-6636-01-aa-usederbyinternals.diff. This patch makes the constructor of BaseDataFileFactory require the usederbyinternals privilege. I am running tests now.



Touches the following files:

----------------

M       java/engine/org/apache/derby/impl/store/raw/data/BaseDataFileFactory.java

Adds the privilege check.

----------------

M       java/testing/org/apache/derbyTesting/functionTests/tests/lang/NoDBInternalsPermissionTest.java

Adds a test case for this.


> The public api of BaseDataFileFactory may allow blackhats to assume elevated privileges.
> ----------------------------------------------------------------------------------------
>
>                 Key: DERBY-6636
>                 URL: https://issues.apache.org/jira/browse/DERBY-6636
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.11.1.1
>            Reporter: Rick Hillegas
>         Attachments: derby-6636-01-aa-usederbyinternals.diff
>
>
> BaseDataFileFactory has a public constructor and a public boot() method. Arbitrary code running in the JVM may be able to instantiate a BaseDataFileFactory outside of Derby's authentication mechanisms and so acquire the ability to read/update Derby-managed data with the privileges granted to Derby.  Arbitrary code may be able to interfere with the normal operation of Derby and may be able to corrupt data.
> This is just an observation based on casual code inspection. It may be that there are mechanisms in place which frustrate these attacks. I have not tried to exploit these potential vulnerabilities myself.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)