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

Nick Dimiduk updated HBASE-30264:
---------------------------------
    Description: The cleanupBulkLoad method in SecureBulkLoadManager constructs 
a Path directly from the bulkToken field of the CleanupBulkLoadRequest and 
passes it to fs.delete(path, true). The bulkToken is expected to be a staging 
directory created by prepareBulkLoad, which always places it under 
\{hbase.rootdir}/staging/. However, cleanupBulkLoad does not verify that the 
supplied path is actually within the staging directory.  (was: The 
cleanupBulkLoad method in SecureBulkLoadManager constructs a Path directly from 
the bulkToken field of the CleanupBulkLoadRequest and passes it to 
fs.delete(path, true). The bulkToken is expected to be a staging directory 
created by prepareBulkLoad, which always places it under {{ 
{hbase.rootdir}/staging/ }}. However, cleanupBulkLoad does not verify that the 
supplied path is actually within the staging directory.)

> Validate bulkToken path in SecureBulkLoadManager.cleanupBulkLoad
> ----------------------------------------------------------------
>
>                 Key: HBASE-30264
>                 URL: https://issues.apache.org/jira/browse/HBASE-30264
>             Project: HBase
>          Issue Type: Task
>          Components: regionserver
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0-beta-2, 2.5.16, 2.6.7
>
>
> The cleanupBulkLoad method in SecureBulkLoadManager constructs a Path 
> directly from the bulkToken field of the CleanupBulkLoadRequest and passes it 
> to fs.delete(path, true). The bulkToken is expected to be a staging directory 
> created by prepareBulkLoad, which always places it under 
> \{hbase.rootdir}/staging/. However, cleanupBulkLoad does not verify that the 
> supplied path is actually within the staging directory.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to