[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1008577: marked as done (bullseye-pu: golang-github-russellhaering-goxmldsig/1.1.0-1+deb11u1)

Your message dated Sat, 09 Jul 2022 11:47:43 +0100
with message-id <2280fe8c78e64b02a6c1d04c6dde5a32e342ba81.camel@adam-barratt.org.uk>
and subject line Closing requests for updates included in 11.4
has caused the Debian Bug report #1008577,
regarding bullseye-pu: golang-github-russellhaering-goxmldsig/1.1.0-1+deb11u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1008577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008577
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian.org@packages.debian.org
Usertags: pu


The attached debdiff for golang-github-russellhaering-goxmldsig fixes
CVE-2020-7711 in Bullseye. This CVE has been marked as no-dsa by the
security team.

  Thorsten

diff -Nru golang-github-russellhaering-goxmldsig-1.1.0/debian/changelog golang-github-russellhaering-goxmldsig-1.1.0/debian/changelog
--- golang-github-russellhaering-goxmldsig-1.1.0/debian/changelog	2021-01-08 00:13:56.000000000 +0100
+++ golang-github-russellhaering-goxmldsig-1.1.0/debian/changelog	2022-03-28 22:32:49.000000000 +0200
@@ -1,3 +1,12 @@
+golang-github-russellhaering-goxmldsig (1.1.0-1+deb11u1) bullseye; urgency=medium
+
+  * CVE-2020-7711
+    null pointer dereference caused by crafted XML signatures
+    (Closes: #968928)
+  * according to ratt, nothing else has to be built
+
+ -- Thorsten Alteholz <debian@alteholz.de>  Mon, 28 Mar 2022 22:32:49 +0200
+
 golang-github-russellhaering-goxmldsig (1.1.0-1) unstable; urgency=medium
 
   * New upstream release (Closes: #971615)
diff -Nru golang-github-russellhaering-goxmldsig-1.1.0/debian/patches/CVE-2020-7711.patch golang-github-russellhaering-goxmldsig-1.1.0/debian/patches/CVE-2020-7711.patch
--- golang-github-russellhaering-goxmldsig-1.1.0/debian/patches/CVE-2020-7711.patch	1970-01-01 01:00:00.000000000 +0100
+++ golang-github-russellhaering-goxmldsig-1.1.0/debian/patches/CVE-2020-7711.patch	2022-03-24 02:38:42.000000000 +0100
@@ -0,0 +1,23 @@
+commit fb23e0af61c023e3a6dae8ad30dbd0f04d8a4d8f
+Merge: 3541f5e ca2b448
+Author: Russell Haering <russellhaering@gmail.com>
+Date:   Fri Aug 27 20:19:01 2021 -0700
+
+    Merge pull request #71 from aporcupine/patch-1
+    
+    Explicitly check for case where SignatureValue is nil
+
+Index: golang-github-russellhaering-goxmldsig-1.1.0/validate.go
+===================================================================
+--- golang-github-russellhaering-goxmldsig-1.1.0.orig/validate.go	2022-03-24 02:38:38.797524728 +0100
++++ golang-github-russellhaering-goxmldsig-1.1.0/validate.go	2022-03-24 02:38:38.797524728 +0100
+@@ -271,6 +271,9 @@
+ 	if !bytes.Equal(digest, decodedDigestValue) {
+ 		return nil, errors.New("Signature could not be verified")
+ 	}
++	if sig.SignatureValue == nil {
++		return nil, errors.New("Signature could not be verified")
++	}
+ 
+ 	// Decode the 'SignatureValue' so we can compare against it
+ 	decodedSignature, err := base64.StdEncoding.DecodeString(sig.SignatureValue.Data)
diff -Nru golang-github-russellhaering-goxmldsig-1.1.0/debian/patches/series golang-github-russellhaering-goxmldsig-1.1.0/debian/patches/series
--- golang-github-russellhaering-goxmldsig-1.1.0/debian/patches/series	1970-01-01 01:00:00.000000000 +0100
+++ golang-github-russellhaering-goxmldsig-1.1.0/debian/patches/series	2022-03-24 02:39:15.000000000 +0100
@@ -0,0 +1 @@
+CVE-2020-7711.patch

--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 11.4

(re-sending with fixed bug numbers)

Hi,

The updates discussed in these bugs were included in today's bullseye
point release.

Regards,

Adam

--- End Message ---
Reply to: