-
Notifications
You must be signed in to change notification settings - Fork 494
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
Upgrade json-smart to avoid security issue #1860
Comments
conker84
added a commit
to conker84/neo4j-apoc-procedures
that referenced
this issue
Apr 22, 2021
conker84
added a commit
to conker84/neo4j-apoc-procedures
that referenced
this issue
Apr 22, 2021
conker84
added a commit
to conker84/neo4j-apoc-procedures
that referenced
this issue
Apr 22, 2021
conker84
added a commit
to conker84/neo4j-apoc-procedures
that referenced
this issue
Apr 22, 2021
conker84
added a commit
that referenced
this issue
Apr 22, 2021
conker84
added a commit
that referenced
this issue
Apr 22, 2021
conker84
added a commit
to conker84/neo4j-apoc-procedures
that referenced
this issue
Apr 22, 2021
conker84
added a commit
that referenced
this issue
Apr 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
net.minidev:json-smart:2.3
is currently transitively used by APOC (4.2 and 4.3, core and full) viacom.jayway.jsonpath:json-path:2.4.0
.This version of
json-smart
(up until 2.4 actually) is currently insecure, as detailed by CVE-2021-27568.The latest
json-path
(2.5.0 at the time of writing) still referencesjson-smart
2.3.Before the next
json-path
release happens (see requests here and there), could we try to enforce the2.4.1
(which fixes the issue) or2.4.5
version ofjson-smart
directly in APOC 4.2 and 4.3 and release them if the build succeeds?The text was updated successfully, but these errors were encountered: