Your message dated Mon, 6 Mar 2023 12:59:42 +0100
with message-id <[email protected]>
and subject line Re: [pkg-php-pear] Bug#1032371: php-phpseclib3: CVE-2023-27560
has caused the Debian Bug report #1032371,
regarding php-phpseclib3: CVE-2023-27560
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 [email protected]
immediately.)
--
1032371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032371
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: php-phpseclib3
Version: 3.0.18-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: [email protected], Debian Security Team <[email protected]>
Hi,
The following vulnerability was published for php-phpseclib3.
CVE-2023-27560[0]:
| Math/PrimeField.php in phpseclib through 2.0.41 has an infinite loop
| with composite primefields.
The official CVE description is right now a bit confusing for me, I'm
assuming the issue is only introduced with [2] wich is in 3.0.0. Is
this correct?
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2023-27560
https://www.cve.org/CVERecord?id=CVE-2023-27560
[1]
https://github.com/phpseclib/phpseclib/commit/6298d1cd55c3ffa44533bd41906caec246b60440
[2]
https://github.com/phpseclib/phpseclib/commit/0398f7a81550a487170edca0ed39f360d4509e83
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 3.0.19-1
Hi Salvatore,
Le 05/03/2023 à 11:04, Salvatore Bonaccorso a écrit :
Source: php-phpseclib3
Version: 3.0.18-1
[…]
The following vulnerability was published for php-phpseclib3.
Thanks, fixed in 3.0.19-1 (but I forgot the Closes: entry :/).
The official CVE description is right now a bit confusing for me, I'm
assuming the issue is only introduced with [2] wich is in 3.0.0. Is
this correct?
That’s indeed my understanding, meaning there is nothing to fix in
stable. There is nothing close to this functionality in php-phpseclib
(version 2) nor php-seclib (version 1).
Regards
taffit
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
