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-website.git
commit 1d19620261a16768503055dfea67b2f956473fc7 Author: Andrea Cosentino <[email protected]> AuthorDate: Mon Jun 15 12:27:06 2026 +0200 Added CVE-2026-49099 Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-49099.md | 17 +++++++++++++++++ content/security/CVE-2026-49099.txt.asc | 31 +++++++++++++++++++++++++++++++ 2 files changed, 48 insertions(+) diff --git a/content/security/CVE-2026-49099.md b/content/security/CVE-2026-49099.md new file mode 100644 index 00000000..e990baea --- /dev/null +++ b/content/security/CVE-2026-49099.md @@ -0,0 +1,17 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-49099" +date: 2026-06-11T10:00:00+02:00 +url: /security/CVE-2026-49099.html +draft: false +type: security-advisory +cve: CVE-2026-49099 +severity: MEDIUM +summary: "Apache Camel: Camel-Salesforce: Non-Camel-prefixed Exchange header constants (sObjectQuery, sObjectSearch, apexUrl, ...) bypass the HTTP header filter, allowing an HTTP client to inject SOQL/SOSL queries, override the target SObject, and redirect Apex REST calls using the connected Salesforce user's permissions" +description: "The camel-salesforce producer resolves its operation parameters - the SOQL query, the SOSL search, the target SObject name and id, the Apex REST URL and method, and the Apex query parameters - from Exchange message headers, reading the header in preference to the value configured on the endpoint (AbstractSalesforceProcessor.getParameter() reads the header first and uses the endpoint configuration only as a fallback). The control-header constants in SalesforceEndpointConfig [...] +mitigation: "Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, routes that set Salesforce operation parameters via the raw header names must use the CamelSalesforce* names (for example CamelSalesforceSObjectQuery and CamelSalesforceApexUrl) instead of the old sObjec [...] +credit: "This issue was discovered by Yu Bao from PayPal" +affected: "From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0." +fixed: 4.14.8, 4.18.3 and 4.21.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23716 refers to the various commits that resolved the issue, and have more details. The fix was merged on main in https://github.com/apache/camel/pull/23887 (commit 3445c57e147da12ccfdde066c06ec5492d8c262b) and backported to camel-4.18.x (commit 578eb2a0a089c94f507853a737d7c46365f0272e) and camel-4.14.x (commit 48880af9d401e8c03473a14bd652ce012b66157b). The fix renames the 39 producer-read camel-salesforce Exchange header const [...] diff --git a/content/security/CVE-2026-49099.txt.asc b/content/security/CVE-2026-49099.txt.asc new file mode 100644 index 00000000..1abacec3 --- /dev/null +++ b/content/security/CVE-2026-49099.txt.asc @@ -0,0 +1,31 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-49099" +date: 2026-06-11T10:00:00+02:00 +url: /security/CVE-2026-49099.html +draft: false +type: security-advisory +cve: CVE-2026-49099 +severity: MEDIUM +summary: "Apache Camel: Camel-Salesforce: Non-Camel-prefixed Exchange header constants (sObjectQuery, sObjectSearch, apexUrl, ...) bypass the HTTP header filter, allowing an HTTP client to inject SOQL/SOSL queries, override the target SObject, and redirect Apex REST calls using the connected Salesforce user's permissions" +description: "The camel-salesforce producer resolves its operation parameters - the SOQL query, the SOSL search, the target SObject name and id, the Apex REST URL and method, and the Apex query parameters - from Exchange message headers, reading the header in preference to the value configured on the endpoint (AbstractSalesforceProcessor.getParameter() reads the header first and uses the endpoint configuration only as a fallback). The control-header constants in SalesforceEndpointConfig [...] +mitigation: "Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, routes that set Salesforce operation parameters via the raw header names must use the CamelSalesforce* names (for example CamelSalesforceSObjectQuery and CamelSalesforceApexUrl) instead of the old sObjec [...] +credit: "This issue was discovered by Yu Bao from PayPal" +affected: "From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0." +fixed: 4.14.8, 4.18.3 and 4.21.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23716 refers to the various commits that resolved the issue, and have more details. The fix was merged on main in https://github.com/apache/camel/pull/23887 (commit 3445c57e147da12ccfdde066c06ec5492d8c262b) and backported to camel-4.18.x (commit 578eb2a0a089c94f507853a737d7c46365f0272e) and camel-4.14.x (commit 48880af9d401e8c03473a14bd652ce012b66157b). The fix renames the 39 producer-read camel-salesforce Exchange header const [...] +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmovx0oACgkQ406fOAL/ +QQC2Dwf/ZfZYUGecOxRHjtR+mkmlXgZ2XNpIcrCNP42dH1blwuSIEiktZi0gEuMW +MYhnIH+82vjcYJdLjT69xFdzChEFh/fHs8NZTK4DqcKo/4XboNUfEQEDdZ6Bcttm +dciFNFcrSDif7BknJakPqvRhaQ9SvDXWXVEn0TkK8DTyJIc6YwnckvyoXuTFIpH1 +uTYtwluPXWkEZi2Vkl52F5l0SW+9pDotVoOavJpZ1cWJMKVoDm7nDRsr4h93klEs +V75W8gTOu+X025G0siFLn4JfeL9Fk8HPA3zfvUTgVbm6Cz9MZM4to5KmASOYoJ7c +10tGQiqkfj30qllgbynZZlqNnrW+8g== +=qJFH +-----END PGP SIGNATURE-----
