pg.ddx.io  GitHub: pgjdbc/pgjdbc (issues + PRs as email threads)  
help / color / mirror / Atom feed
[pgjdbc/pgjdbc] issue #4532: Release with scram-client 3.4 (GHSA-p9jg-fcr6-3mhf) for version-based scanners
3+ messages / 2 participants
[nested] [flat]

* [pgjdbc/pgjdbc] issue #4532: Release with scram-client 3.4 (GHSA-p9jg-fcr6-3mhf) for version-based scanners
@ 2026-11-16 19:08 "jphalip (@jphalip)" <noreply+jphalip@github.com>
  0 siblings, 0 replies; 3+ messages in thread

From: jphalip (@jphalip) @ 2026-11-16 19:08 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <noreply+pgjdbc-pgjdbc@github.com>

Hello there. Our vulnerability scanners are flagging 42.7.14 because it shades `com.ongres.scram:scram-client` and `scram-common` 3.2, which are affected by [GHSA-p9jg-fcr6-3mhf](https://github.com/advisories/GHSA-p9jg-fcr6-3mhf) (CVE-2026-53712, fixed in 3.3).

We know 42.7.12 already fixes the downgrade in the driver itself (GHSA-j92g-9f8w-j867, #4272), independently of the scram-client version. Unfortunately, the scanners only compare library versions, so the jar is blocked in our release pipelines until a release bundles scram 3.3 or later.

We saw that #4298 was closed and that #4428 keeps minor ongres bumps for pgJDBC minor releases. Given that this is a security advisory, would you consider an exception for 42.7.15? If not, is there a rough date for the next minor release?

We're happy to send the PR. From a quick look, it would bump scram-client to 3.4 (3.3 has a regression that 3.4 fixes) and stringprep/saslprep to 2.4, and replace the deprecated `TlsServerEndpoint.getChannelBindingData` in `ScramAuthenticator`, which currently fails the build under `-Werror`, with `getChannelBindingHash`. scram 3.4 still targets Java 8. Let us know which branch you'd want it against.

Thanks!


^ permalink  raw  [nested|flat] 3+ messages in thread

* Re: [pgjdbc/pgjdbc] issue #4532: Release with scram-client 3.4 (GHSA-p9jg-fcr6-3mhf) for version-based scanners
@ 2026-11-16 19:50 ` "vlsi (@vlsi)" <noreply+vlsi@github.com>
  1 sibling, 0 replies; 3+ messages in thread

From: vlsi (@vlsi) @ 2026-11-16 19:50 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <noreply+pgjdbc-pgjdbc@github.com>

Hi. Could you please ask ongres scram team to release a patch version with the fix? I guess having a request from end users would justify the need for a patch release.

^ permalink  raw  [nested|flat] 3+ messages in thread

* Re: [pgjdbc/pgjdbc] issue #4532: Release with scram-client 3.4 (GHSA-p9jg-fcr6-3mhf) for version-based scanners
@ 2026-11-16 21:17 ` "jphalip (@jphalip)" <noreply+jphalip@github.com>
  1 sibling, 0 replies; 3+ messages in thread

From: jphalip (@jphalip) @ 2026-11-16 21:17 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <noreply+pgjdbc-pgjdbc@github.com>

Thanks @vlsi, that makes sense. I've asked the ongres team for a 3.2.1 patch release here: https://github.com/ongres/scram/issues/152. I'll update this issue when there's news.

^ permalink  raw  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2026-11-16 21:17 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-11-16 19:08 [pgjdbc/pgjdbc] issue #4532: Release with scram-client 3.4 (GHSA-p9jg-fcr6-3mhf) for version-based scanners "jphalip (@jphalip)" <noreply+jphalip@github.com>
2026-11-16 19:50 ` "vlsi (@vlsi)" <noreply+vlsi@github.com>
2026-11-16 21:17 ` "jphalip (@jphalip)" <noreply+jphalip@github.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox