Fix security, CI, and dependency issues in JDBC driver #2331
+23
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: This PR was created with AI tools and a human.
Security audit of the JDBC driver source code (16 main + 5 test Java files). The driver is a pure type-mapping layer (PGobject/agtype serialization only) with no query-building APIs, so it has minimal attack surface. No application-level vulnerabilities were found.
Update all dependencies to address critical vulnerabilities:
Note: postgresql 42.7.7+ also fixes CVE-2025-49146 (High: auth bypass with channelBinding=require). Version 42.7.5 was chosen as a conservative update to fix the Critical CVE while minimizing risk from protocol changes in newer releases.
Fix root cause of CI test flakiness in BaseDockerizedTest:
modified: drivers/jdbc/gradle/wrapper/gradle-wrapper.properties
modified: drivers/jdbc/lib/build.gradle.kts
modified: drivers/jdbc/lib/src/test/java/org/apache/age/jdbc/BaseDockerizedTest.java