[ 
https://issues.apache.org/jira/browse/HADOOP-19687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020318#comment-18020318
 ] 

ASF GitHub Bot commented on HADOOP-19687:
-----------------------------------------

rohit-kb opened a new pull request, #7965:
URL: https://github.com/apache/hadoop/pull/7965

   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   
   1. Bumping nimbus-jose-jwt to 10.4 due to CVEs
   2. com.github.stephenc.jcip:jcip-annotations is being shaded and is no more 
a transitive dependency from nimbus starting from versions 9.38, so we can add 
it as an explicit dependency.
   
   ### How was this patch tested?
   
   
   ### For code changes:
   
   - [ ] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> Upgrade nimbus-jose-jwt to 10.0.2+ due to CVE-2025-53864
> --------------------------------------------------------
>
>                 Key: HADOOP-19687
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19687
>             Project: Hadoop Common
>          Issue Type: Task
>            Reporter: Rohit Kumar
>            Priority: Major
>
> *CVE-2025-53864:*
> Connect2id Nimbus JOSE + JWT before 10.0.2 allows a remote attacker to cause 
> a denial of service via a deeply nested JSON object supplied in a JWT claim 
> set, because of uncontrolled recursion. NOTE: this is independent of the Gson 
> 2.11.0 issue because the Connect2id product could have checked the JSON 
> object nesting depth, regardless of what limits (if any) were imposed by Gson.
> Severity: 6.9 (medium)



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to