[
https://issues.apache.org/jira/browse/DERBY-6636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046453#comment-14046453
]
Dag H. Wanvik commented on DERBY-6636:
--------------------------------------
I tried to instantiate a new DBFF object and call "boot" on it but didn't get
very far, cf. this stack trace:
{code}
TopService.findModuleInstance:237
TopService.inService:430
BaseMonitor.findTopService:556
BaseMonitor.getServiceType:517
FileMonitor.getServiceType:44
BaseDataFileFactory.boot:274
FooApp.main:38
{code}
because the monitor's "getService" method returns null (the object isn't in the
list search through by topService), so
a null is returned, leading to a NPE in BDFF line 279 since "ps" is null. I
have not tried the other methods on BDFF for mischief.
> 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.0.0
> Reporter: Rick Hillegas
>
> 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.2#6252)
