com.jayway.jsonpath:json-path vulnerabilities
A library to query and verify JSON
- Registry
- Maven
- Latest
- 3.0.0
- License
- The Apache Software License, Version 2.0
1 known advisory
The latest version, 3.0.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
mvn versions:use-dep-version -Dincludes=com.jayway.jsonpath:json-path -DdepVersion=3.0.0 -DforceVersion=trueIs your project on an affected com.jayway.jsonpath:json-path?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for com.jayway.jsonpath:json-path
json-path Out-of-bounds Write vulnerability
- Affected
- >=2.2.0 <2.9.0
- Fixed in
- 2.9.0
Is your com.jayway.jsonpath:json-path version vulnerable?
- com.jayway.jsonpath:json-path 3.0No known advisories in 3.0.0
- com.jayway.jsonpath:json-path 2.10No known advisories in 2.10.0
- com.jayway.jsonpath:json-path 2.9No known advisories in 2.9.0
- com.jayway.jsonpath:json-path 2.81 advisory in 2.8.0
- com.jayway.jsonpath:json-path 2.71 advisory in 2.7.0
- com.jayway.jsonpath:json-path 2.61 advisory in 2.6.0
- com.jayway.jsonpath:json-path 2.51 advisory in 2.5.0
- com.jayway.jsonpath:json-path 1.2No known advisories in 1.2.0
- com.jayway.jsonpath:json-path 1.1No known advisories in 1.1.0
- com.jayway.jsonpath:json-path 1.0No known advisories in 1.0.0
Which of your client projects still run an old com.jayway.jsonpath:json-path?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.