Re: libspring-java support
On 01/04/2022 11:50, Emilio Pozuelo Monfort wrote:
On 03/12/2021 23:50, Markus Koschany wrote:
Am Freitag, dem 03.12.2021 um 14:28 +0100 schrieb Sylvain Beucler:
This year I worked on libspring-java twice for LTS&ELTS. In both case
upstream provided limited information for the CVEs, and for 5 of them
we're unable to determine the fixes.
Upstream declined to provide information to identify the fixes (which in
turn would allow us to determine whether stretch and jessie are
affected, and backport the fixes if needed).
They made clear that they wouldn't provide this information even if
paid, confirming they apply a security-by-obscurity strategy similar to
I exchanged with the Debian security team after they witnessed the last
exchanges above, and 2 weeks ago they concluded the latest CVE was minor
and no action was needed right now. I insisted about the other, prior
unfixable CVEs (1/4 impacting buster) but they haven't answered yet.
I think we're not in capacity to offer further security support for
libspring-java for LTS and ELTS, but I'd like to hear from other team
members, especially if they work in the Java team (Markus?) - what do
I have made similar experiences like you when I contacted upstream and
for more information about previous CVE. I agree with you that their
makes future security support for us nearly impossible. Currently the
purpose of libspring-java is to build other software from source. We
any application or web project that depends on Spring and exposes
users to the
currently unfixed CVE which means the current status of all CVE in
Stretch/Buster/Bullseye (no-dsa/minor) is correct. It is also very
that Java developers who use Spring/Spring Boot for their web
depend on one of our Debian packages.
In my opinion it is OK to ignore the currently known CVE. I would support
adding libspring-java to the list of unsupported packages because of
of upstream support. We, as the Java team, should make this clear by
libspring-java in the next release notes for Debian 12.
Looks like Spring was marked as EOL in the security-tracker and
debian-security-support git, but never uploaded to stretch or announced
on debian-lts-announce (unless I missed it). I think this (as well as
other packages recently EOL'ed) should be announced there, so users are
aware. Should we add this to dla-needed so that someone can take care of
Sure, go ahead.
Holger, can you clarify if you want the LTS team to handle
debian-security-support backports to stretch, or if you intend to do it
which AFAIU was only uploaded to unstable)