Skip to content

Manage Jackson with jackson-bom 2.23.0 - #302

Open
deepika-lalwani123 wants to merge 3 commits into
developfrom
vuln/dbd-3-jackson-bom-2.18.12
Open

deepika-lalwani123 wants to merge 3 commits into
developfrom
vuln/dbd-3-jackson-bom-2.18.12

Conversation

@deepika-lalwani123

@deepika-lalwani123 deepika-lalwani123 commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Manage Jackson with jackson-bom 2.23.0

Stacked PR: this branch is built on top of #300, #301. Against develop the diff includes those commits; please review only the top commit b4bd0a0d43. Merge after #301.

Repo: data-integrations/database-delta-plugins
Base: develop (stacked)
Commit: b4bd0a0
Part of the CVE fixes for the CDAP 6.11.2 patch release (container image scanning).

debezium 1.9.7.Final and Kafka Connect 3.2.0 bring a mix of old Jackson
jars (jackson-core 2.13.2, jackson-databind 2.13.2.2,
jackson-annotations / jackson-datatype-jdk8 2.12.6,
jackson-datatype-jsr310 2.13.2) that container image scanning reports in
/opt/cdap/master/artifacts/{mysql,sqlserver}-delta-plugins-*.jar/lib/
(jackson-databind 13 rows and jackson-core 3 rows per plugin).

Import com.fasterxml.jackson:jackson-bom 2.23.0 in the root
dependencyManagement so every Jackson module resolves to 2.23.0
(jackson-annotations to 2.23, which has no patch number since 2.20).
debezium stays at 1.9.7.Final (2.x needs Java 11).

Versions:

  • jackson-core 2.13.2, jackson-databind 2.13.2.2, jackson-datatype-jdk8
    2.12.6, jackson-datatype-jsr310 2.13.2 -> 2.23.0 (jackson-bom import,
    jackson.version)
  • jackson-annotations 2.12.6 -> 2.23 (via the BOM)

Risk: medium. Jackson 2.15+ adds stream read limits; 2.19 - 2.23 are
drop-in 2.x releases that still target Java 8. debezium uses Jackson
for its Document / history JSON and Kafka Connect for JsonConverter.

Testing: JDK 8.

  • mvn package -DskipTests: BUILD SUCCESS for all modules.
  • mvn dependency:tree -Dincludes=com.fasterxml.jackson: every Jackson
    artifact in all modules is 2.23.0 (jackson-annotations 2.23).

The root POM declared ch.qos.logback:logback-classic 1.0.9 at compile
scope, so mysql-delta-plugins and sqlserver-delta-plugins packaged
logback-classic and logback-core 1.0.9 under lib/. Image scanning of
gcr.io/cdapio/cdap reports these jars under
/opt/cdap/master/artifacts/{mysql,sqlserver}-delta-plugins-*.jar/lib/.
No plugin main code uses logback; CDAP supplies the slf4j binding at
runtime. The only logback references are the logback-test.xml test
resources, which are ignored when no logback is on the test classpath.

delta-api 0.9.0 leaks junit 4.12 at compile scope (fixed at the source
in data-integrations/delta DL-1). Exclude it here so junit 4.12 is no
longer packaged (lib/junit-4.12.jar in mysql-delta-plugins), and add
junit 4.13.2 at test scope for the unit tests that relied on it.

Versions:
- logback-classic / logback-core 1.0.9 -> removed (root pom)
- junit 4.12 (compile, via delta-api) -> excluded; junit 4.13.2 test
  scope (root pom)

Bugs: b/578434136, b/578581195. Plugins side done for the junit 4.12
row of b/578455300 (closes once DL-1 and DS-1 land).

Risk: low. Packaging-only change; no code change. Plugin logging still
goes through slf4j to the CDAP-provided binding.

Testing: JDK 8. mvn clean package -DtestSourceLocation=src/test/java
(develop never compiles src/test/java by default because
testSourceDirectory is ${testSourceLocation}): BUILD SUCCESS, Checkstyle
0 violations; delta-plugins-common RecordsTest, RuntimeArgumentsTest
(3 tests) and sqlserver SqlServerTableAssessorTest,
SqlServerRecordConsumerTest (7 tests) pass. mysql-delta-plugins has
only *IntegrationTest (Docker MySQL); integration and e2e tests not
run. mvn dependency:tree -Dincludes=junit,ch.qos.logback now shows only
junit:junit:4.13.2:test in every module (was logback-classic 1.0.9
compile and junit 4.12 compile). unzip -l of the built mysql/sqlserver
plugin jars shows no logback-*, junit-* or hamcrest-* under lib/
(develop: logback-classic/core 1.0.9 in both, junit-4.12 and
hamcrest-core-1.3 in mysql-delta-plugins).
mysql-delta-plugins and sqlserver-delta-plugins pin kafka-clients
3.9.1, which image scanning of gcr.io/cdapio/cdap reports in
/opt/cdap/master/artifacts/{mysql,sqlserver}-delta-plugins-*.jar/lib/
kafka-clients-3.9.1.jar. 3.9.2 is the fixed patch release and the last
Java 8 line.

kafka-clients 3.9.2 depends on at.yawk.lz4:lz4-java 1.10.1 (the
maintained lz4-java fork, same net.jpountz packages) instead of
org.lz4:lz4-java 1.8.0. Both are runtime scope and the bundle plugin
embeds only compile scope, so neither lz4 jar is packaged (before or
after) and no duplicate net.jpountz classes appear; no lz4 exclusion
is needed.

Versions:
- kafka-clients 3.9.1 -> 3.9.2 (mysql-delta-plugins,
  sqlserver-delta-plugins)

Bugs: Plugins side done for the kafka-clients 3.9.1 rows (plan DBD-2;
the plan credits 0 bugs closed alone, 1 with other tracks).

Risk: low. Same-line patch release. debezium 1.9.7 keeps its Kafka
Connect 3.2.0 API jars; kafka-clients was already 3.9.1 next to them.

Testing: JDK 8. mvn -T 4 clean package -DtestSourceLocation=src/test/java:
BUILD SUCCESS, Checkstyle 0 violations, delta-plugins-common (3 tests)
and sqlserver-delta-plugins (7 tests) pass; Docker-based
*IntegrationTest and e2e not run. mvn dependency:tree
-Dincludes=org.apache.kafka:kafka-clients,org.lz4,at.yawk.lz4 on mysql
and sqlserver: kafka-clients 3.9.2 compile -> at.yawk.lz4:lz4-java
1.10.1 runtime; no 3.9.1. unzip -l: lib/kafka-clients-3.9.2.jar in both
plugin jars, no lz4 jar and no net/jpountz classes.
@vikasrathee-cs
vikasrathee-cs force-pushed the vuln/dbd-3-jackson-bom-2.18.12 branch from b4bd0a0 to 642f66c Compare November 20, 2026 08:52
debezium 1.9.7.Final and Kafka Connect 3.2.0 bring a mix of old Jackson
jars (jackson-core 2.13.2, jackson-databind 2.13.2.2,
jackson-annotations / jackson-datatype-jdk8 2.12.6,
jackson-datatype-jsr310 2.13.2) that container image scanning reports in
/opt/cdap/master/artifacts/{mysql,sqlserver}-delta-plugins-*.jar/lib/
(jackson-databind 13 rows and jackson-core 3 rows per plugin).

Import com.fasterxml.jackson:jackson-bom 2.23.0 in the root
dependencyManagement so every Jackson module resolves to 2.23.0
(jackson-annotations to 2.23, which has no patch number since 2.20).
debezium stays at 1.9.7.Final (2.x needs Java 11).

Versions:
- jackson-core 2.13.2, jackson-databind 2.13.2.2, jackson-datatype-jdk8
  2.12.6, jackson-datatype-jsr310 2.13.2 -> 2.23.0 (jackson-bom import,
  jackson.version)
- jackson-annotations 2.12.6 -> 2.23 (via the BOM)

Risk: medium. Jackson 2.15+ adds stream read limits; 2.19 - 2.23 are
drop-in 2.x releases that still target Java 8. debezium uses Jackson
for its Document / history JSON and Kafka Connect for JsonConverter.

Testing: JDK 8.
- mvn package -DskipTests: BUILD SUCCESS for all modules.
- mvn dependency:tree -Dincludes=com.fasterxml.jackson: every Jackson
  artifact in all modules is 2.23.0 (jackson-annotations 2.23).
@deepika-lalwani123
deepika-lalwani123 force-pushed the vuln/dbd-3-jackson-bom-2.18.12 branch from 642f66c to c9c7064 Compare November 21, 2026 12:02
@deepika-lalwani123 deepika-lalwani123 changed the title Manage Jackson with jackson-bom 2.18.12 Manage Jackson with jackson-bom 2.23.0 Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant