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

Rajmund Takacs updated NIFI-13627:
----------------------------------
    Description: 
Applies to 1.x support branch.

{{azure.sdk.bom.version}} should be {{1.2.25+}}
{{msal4j.version}} should be {{1.16.1+}}

CVEs fixed in these versions:
* CVE-2023-36415
* CVE-2024-35255
 

NIFI-13574 fixed the same CVEs in {{nifi-azure-bundle,}} the CVEs have to be 
fixed for {{nifi-property-protection-azure}} as well.


  was:
Applies to 1.x support branch.

Upgrade to 26.40.0+, to fix the following CVEs, caused by threetenbp 1.6.8:
 * CVE-2024-23082
 * CVE-2024-23081

 

NIFI-13573 fixed the same CVEs in nifi-gcp-bundle, the CVEs have to be fixed 
for nifi-property-protection-gcp as well.

Suppression list needs to be extended with threeten since CVE-2024-23081 and 
CVE-2024-23082 are still shown as vulnerability after the version upgrade. 
(This suppression is also included in NiFi 2.x, main branch 
[https://github.com/apache/nifi/blob/main/nifi-dependency-check-maven/suppressions.xml#L268]).

 


> Bump azure-sdk-bom to 1.2.25, and msal4j to 1.16.1 for 
> nifi-property-protection-azure
> -------------------------------------------------------------------------------------
>
>                 Key: NIFI-13627
>                 URL: https://issues.apache.org/jira/browse/NIFI-13627
>             Project: Apache NiFi
>          Issue Type: Task
>    Affects Versions: 1.28.0
>            Reporter: Rajmund Takacs
>            Assignee: Zsihovszki Krisztina
>            Priority: Major
>             Fix For: 1.28.0
>
>
> Applies to 1.x support branch.
> {{azure.sdk.bom.version}} should be {{1.2.25+}}
> {{msal4j.version}} should be {{1.16.1+}}
> CVEs fixed in these versions:
> * CVE-2023-36415
> * CVE-2024-35255
>  
> NIFI-13574 fixed the same CVEs in {{nifi-azure-bundle,}} the CVEs have to be 
> fixed for {{nifi-property-protection-azure}} as well.



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

Reply via email to