[
https://issues.apache.org/jira/browse/DERBY-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas resolved DERBY-6641.
----------------------------------
Resolution: Not a Problem
Fix Version/s: 10.12.0.0
After the work on DERBY-6648, I no longer see a way for user code to get its
hands on the LogFactory. I think we can close this bug.
> Application code may be able to use the public LogToFile class to interfere
> with Derby's operation.
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-6641
> URL: https://issues.apache.org/jira/browse/DERBY-6641
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.11.1.1
> Reporter: Rick Hillegas
> Fix For: 10.12.0.0
>
>
> With a little work, I think that an application could dig up the LogFactory
> and cast it to LogToFile. This could give the application elevated privileges
> to overwrite sensitive Derby-managed data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
