This is an automated email from the ASF dual-hosted git repository.

oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 513d0e18a4b5 CAMEL-23942: sync Azure Storage fileDir containment note 
to the 4.18/4.14 upgrade guides on main (#24585)
513d0e18a4b5 is described below

commit 513d0e18a4b54220f6c12ab84d3bea9641f9776d
Author: Andrea Cosentino <[email protected]>
AuthorDate: Fri Jul 10 15:22:38 2026 +0200

    CAMEL-23942: sync Azure Storage fileDir containment note to the 4.18/4.14 
upgrade guides on main (#24585)
    
    Documents on main the containment behavior backported to camel-4.18.x 
(#24581)
    and camel-4.14.x (#24582), per the backport upgrade-guide policy.
    
    Signed-off-by: Andrea Cosentino <[email protected]>
    Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc        | 10 ++++++++++
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc        | 10 ++++++++++
 2 files changed, 20 insertions(+)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
index 6eb32e3be705..34e0f9caf7d3 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
@@ -1575,3 +1575,13 @@ non-`Camel`-prefixed application headers and map them to 
the corresponding
 the `salesforce:` `to`. As defence-in-depth, strip inbound Camel-internal 
headers
 arriving from untrusted producers with `removeHeaders("CamelSalesforce*")` (or 
the
 broader `removeHeaders("Camel*")`) before the producer.
+
+=== camel-azure-storage-blob / camel-azure-storage-datalake - download 
contained within fileDir
+
+When `fileDir` is configured, the Azure Storage Blob and DataLake consumers 
now ensure the downloaded
+local file stays within the configured directory, so a remote object name 
containing `../` sequences
+can no longer resolve to a path outside it. This is consistent with the 
containment already performed
+by the file-based consumers.
+
+Ordinary object names are unaffected. A name that resolves outside `fileDir` 
is now rejected with an
+`IllegalArgumentException`.
diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index ee9427c87c93..df57833f08ea 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -1876,3 +1876,13 @@ is migrated to JSON the next time the metadata is 
updated.
 
 Because older versions cannot read the new JSON metadata, downgrading after 
new key metadata has been
 written is not supported.
+
+=== camel-azure-storage-blob / camel-azure-storage-datalake - download 
contained within fileDir
+
+When `fileDir` is configured, the Azure Storage Blob and DataLake consumers 
now ensure the downloaded
+local file stays within the configured directory, so a remote object name 
containing `../` sequences
+can no longer resolve to a path outside it. This is consistent with the 
containment already performed
+by the file-based consumers.
+
+Ordinary object names are unaffected. A name that resolves outside `fileDir` 
is now rejected with an
+`IllegalArgumentException`.

Reply via email to