UTF8DataInputJsonParser._reportInvalidToken() in FasterXML jackson-core builds the offending-token text for its error message by appending Java identifier characters to a StringBuilder in a loop that has no upper bound. Unlike the three sibling parser implementations, including UTF8StreamJsonParser, it never consults ErrorReportConfiguration.getMaxErrorTokenLength() (default 256). A malformed token supplied to a parser created through JsonFactory.createParser(DataInput) is therefore accumulated in full. No StreamReadConstraints setting mitigates this: maxDocumentLength cannot be applied to DataInput sources at all, and maxStringLength does not cover this path because the accumulation bypasses ReadConstrainedTextBuffer. The reporter measured a 20,000,109-character exception message from a 20-million-character malformed token on the DataInput path, against 367 characters for identical input on the InputStream path. Scaling the payload drives the StringBuilder, which also incurs byte-to-char expansion and internal array doubling, to many times the raw payload size and can trigger OutOfMemoryError for the whole JVM. UTF8DataInputJsonParser was introduced in 2.8.0 together with createParser(DataInput); releases before 2.8.0 do not contain the affected class.
| Vendor | Product | Versions |
|---|---|---|
| fasterxml | jackson-core | maven/com.fasterxml.jackson.core:jackson-core: >= 2.19.0, <= 2.21.6, maven/com.fasterxml.jackson.core:jackson-core: >= 2.22.0, <= 2.22.2, maven/tools.jackson.core:jackson-core: >= 3.0.0, <= 3.1.6, maven/tools.jackson.core:jackson-core: >= 3.2.0, <= 3.2.2, maven/com.fasterxml.jackson.core:jackson-core: >= 2.8.0, <= 2.18.10 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| atlassian | fisheye | cert_advisory | 90% |
| atlassian | crucible | cert_advisory | 90% |
| atlassian | bamboo | cert_advisory | 90% |
| atlassian | confluence | cert_advisory | 90% |
| atlassian | bitbucket | cert_advisory | 90% |
Loading…