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/10/03 14:46:34 UTC

[jira] [Resolved] (DERBY-6635) OptimizerTracer.unloadTool() could be used to write garbage over Derby data files.

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

Rick Hillegas resolved DERBY-6635.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 10.12.0.0
                   10.11.1.2

> OptimizerTracer.unloadTool() could be used to write garbage over Derby data files.
> ----------------------------------------------------------------------------------
>
>                 Key: DERBY-6635
>                 URL: https://issues.apache.org/jira/browse/DERBY-6635
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.11.1.1
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.11.1.2, 10.12.0.0
>
>         Attachments: derby-6635-01-aa-noOverwrite.diff, derby-6635-01-ab-noOverwrite.diff
>
>
> I don't see any checks in place to prevent this method from writing its output file into the log or sego directories or even over service.properties. Fortunately, only the DBO can run this procedure by default.



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