[
https://issues.apache.org/jira/browse/HBASE-30264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18093023#comment-18093023
]
Hudson commented on HBASE-30264:
--------------------------------
Results for branch branch-3
[build #584 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/584/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/584/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/584/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> 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)
