jackson-databind resolves attacker-controlled URI schemes when deserializing java.nio.file.Path
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.18.10, 2.21.6, 2.22.2, 3.1.6, 3.2.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
jackson-databind's deserializer for java.nio.file.Path resolves an attacker-supplied URI without restricting the URI scheme. In JDKFromStringDeserializer.NioPathHelper.deserialize, a string bound from untrusted JSON is passed to new URI(value) and then to Path.of(uri). When that throws FileSystemNotFoundException, the code enumerates ServiceLoader<FileSystemProvider> and calls provider.getPath(uri) on the first provider whose scheme matches the attacker-chosen scheme. Untrusted JSON can therefore select and drive an arbitrary registered FileSystemProvider during readValue under a default JsonMapper, and forces provider class loading at the same time. With only the JDK built-in providers (file, jar/zipfs) present, the resolved path is inert and no mount or network I/O occurs; further impact requires a side-effecting third-party FileSystemProvider on the classpath. This affects com.fasterxml.jackson.core:jackson-databind from 2.8.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2. Binding java.nio.file.Path from untrusted JSON should be avoided regardless of version.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- com.fasterxml.jackson.core:jackson-databind
From 2.8.0 · fixed in 2.18.10; From 2.19.0 · fixed in 2.21.6; From 2.22.0 · fixed in 2.22.2
- tools.jackson.core:jackson-databind
From 3.0.0 · fixed in 3.1.6; From 3.2.0 · fixed in 3.2.2
- tools.jackson.core:jackson-databindMaven
From 3.0.0 · fixed in 3.1.6
- tools.jackson.core:jackson-databindMaven
From 3.2.0 · fixed in 3.2.2
- com.fasterxml.jackson.core:jackson-databindMaven
From 2.8.0 · fixed in 2.18.10
- com.fasterxml.jackson.core:jackson-databindMaven
From 2.19.0 · fixed in 2.21.6
- com.fasterxml.jackson.core:jackson-databindMaven
From 2.22.0 · fixed in 2.22.2