Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2024-57699 in net.minidev:[email protected] #908

Closed
mehradrafigh opened this issue Feb 12, 2025 · 6 comments
Closed

CVE-2024-57699 in net.minidev:[email protected] #908

mehradrafigh opened this issue Feb 12, 2025 · 6 comments
Labels
Dependencies Pull requests that update a dependency file P2 Normal priority items, should be done after P1

Comments

@mehradrafigh
Copy link

There is a potential security issue in net.minidev:[email protected] which is listed on Maven Central and can be found via Snyk.

net.minidev.json-smart already released the fix with version 2.5.2

Please consider updating the dependency as soon as it is available through Maven Central.

@Avery-Dunn
Copy link
Collaborator

Hello @mehradrafigh : Thanks for letting us know, we'll use 2.5.2 of json-smart in our next release.

For now, last week we downgraded to a json-smart version which didn't seem to have the CVE and released 1.19.0 our our library: #905

@Avery-Dunn Avery-Dunn added Dependencies Pull requests that update a dependency file P2 Normal priority items, should be done after P1 labels Feb 12, 2025
@petarov
Copy link

petarov commented Feb 18, 2025

The way I understand it json-smart:2.5.1 actually is a dependency of com.nimbusds:oauth2-oidc-sdk:11.18, so even if downgraded in msal4j:1.19.0 build tools like Gradle will resolve the higher version unless manually enforced in the dependent project.

net.minidev:json-smart:2.5.1
\--- com.nimbusds:oauth2-oidc-sdk:11.18
     \--- com.microsoft.azure:msal4j:1.19.0
          +--- compileClasspath (requested com.microsoft.azure:msal4j:{require 1.19.0; reject _})
          +--- com.azure:azure-identity:1.14.2 (requested com.microsoft.azure:msal4j:1.17.2)
          |    \--- compileClasspath (requested com.azure:azure-identity:{require 1.14.2; reject _})
          \--- com.microsoft.azure:msal4j-persistence-extension:1.3.0 (requested com.microsoft.azure:msal4j:1.15.0)
               \--- com.azure:azure-identity:1.14.2 (*)

net.minidev:json-smart:2.4.11 -> 2.5.1
\--- com.microsoft.azure:msal4j:1.19.0
     +--- compileClasspath (requested com.microsoft.azure:msal4j:{require 1.19.0; reject _})
     +--- com.azure:azure-identity:1.14.2 (requested com.microsoft.azure:msal4j:1.17.2)
     |    \--- compileClasspath (requested com.azure:azure-identity:{require 1.14.2; reject _})
     \--- com.microsoft.azure:msal4j-persistence-extension:1.3.0 (requested com.microsoft.azure:msal4j:1.15.0)
          \--- com.azure:azure-identity:1.14.2 (*)

@Avery-Dunn
Copy link
Collaborator

Avery-Dunn commented Feb 18, 2025

@petarov : I'm more familiar with Maven which prioritizes versions directly mentioned in the pom file, so if you just had msal4j (and oauth2-oidc-sdk was a transitive dependency through it) then I believe it would pull in json-smart:2.4.11. But if you had multiple json-smart transitive dependencies then it probably would default to the highest option.

Either way, at the time we released msal4j:1.19.0 the newest non-vulnerable version was json-smart:2.4.11. For the next release we'll add more exclusions to transitive dependencies to better control what versions are used, and other upcoming releases we're planning on removing as many dependencies as we can anyway: #909

@petarov
Copy link

petarov commented Feb 18, 2025

Yes, you're right. There is a discrepancy in Maven vs. Gradle resolution strategy. I haven't used Maven for a while and forgot that it was different there. Thanks, looking forward to the next release.

@dfa1
Copy link

dfa1 commented Feb 27, 2025

would it be possible to fix and release this soon?

@Avery-Dunn
Copy link
Collaborator

Avery-Dunn commented Feb 28, 2025

Hey all, msal4j 1.19.1 was released yesterday to bump the json-smart and oauth2-oidc-sdk versions: https://mvnrepository.com/artifact/com.microsoft.azure/msal4j/1.19.1

There shouldn't be any more issues with the CVE, but if there are still problems or any other issues feel free to re-open this thread or start a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dependencies Pull requests that update a dependency file P2 Normal priority items, should be done after P1
Projects
None yet
Development

No branches or pull requests

4 participants