• Bug#1060407: Multiple security issues

    From Moritz Muehlenhoff@21:1/5 to All on Wed Jan 10 20:40:01 2024
    Source: gtkwave
    Version: 3.3.116-1
    Severity: grave
    Tags: security
    X-Debbugs-Cc: Debian Security Team <team@security.debian.org>

    A very thorough security audit of gtkwave unveiled a total of 82 security issues in gtkwave, all fixed in 3.3.118:

    CVE-2023-32650 CVE-2023-34087 CVE-2023-34436 CVE-2023-35004
    CVE-2023-35057 CVE-2023-35128 CVE-2023-35702 CVE-2023-35703
    CVE-2023-35704 CVE-2023-35955 CVE-2023-35956 CVE-2023-35957
    CVE-2023-35958 CVE-2023-35959 CVE-2023-35960 CVE-2023-35961
    CVE-2023-35962 CVE-2023-35963 CVE-2023-35964 CVE-2023-35969
    CVE-2023-35970 CVE-2023-35989 CVE-2023-35992 CVE-2023-35994
    CVE-2023-35995 CVE-2023-35996 CVE-2023-35997 CVE-2023-36746
    CVE-2023-36747 CVE-2023-36861 CVE-2023-36864 CVE-2023-36915
    CVE-2023-36916 CVE-2023-37282 CVE-2023-37416 CVE-2023-37417
    CVE-2023-37418 CVE-2023-37419 CVE-2023-37420 CVE-2023-37442
    CVE-2023-37443 CVE-2023-37444 CVE-2023-37445 CVE-2023-37446
    CVE-2023-37447 CVE-2023-37573 CVE-2023-37574 CVE-2023-37575
    CVE-2023-37576 CVE-2023-37577 CVE-2023-37578 CVE-2023-37921
    CVE-2023-37922 CVE-2023-37923 CVE-2023-38583 CVE-2023-38618
    CVE-2023-38619 CVE-2023-38620 CVE-2023-38621 CVE-2023-38622
    CVE-2023-38623 CVE-2023-38648 CVE-2023-38649 CVE-2023-38650
    CVE-2023-38651 CVE-2023-38652 CVE-2023-38653 CVE-2023-38657
    CVE-2023-39234 CVE-2023-39235 CVE-2023-39270 CVE-2023-39271
    CVE-2023-39272 CVE-2023-39273 CVE-2023-39274 CVE-2023-39275
    CVE-2023-39316 CVE-2023-39317 CVE-2023-39413 CVE-2023-39414
    CVE-2023-39443 CVE-2023-39444

    Let's first fix unstable and then we can simple build 3.3.118
    for stable-security and oldstable-security as well.

    Full details in these advisories from TALOS: https://talosintelligence.com/vulnerability_reports/TALOS-2023-1777 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1783 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1785 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1786 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1789 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1790 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1791 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1792 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1793 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1797 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1798 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1803 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1804 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1805 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1806 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1807 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1810 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1811 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1812 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1813 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1814 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1815 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1816 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1817 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1818 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1819 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1820 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1821 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1822 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1823 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1824 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1826 https://talosintelligence.com/vulnerability_reports/TALOS-2023-1827

    Cheers,
    Moritz

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adrian Bunk@21:1/5 to Moritz Muehlenhoff on Sat Mar 16 00:10:01 2024
    On Wed, Jan 10, 2024 at 08:36:38PM +0100, Moritz Muehlenhoff wrote:
    Source: gtkwave
    Version: 3.3.116-1
    Severity: grave
    Tags: security
    X-Debbugs-Cc: Debian Security Team <team@security.debian.org>

    A very thorough security audit of gtkwave unveiled a total of 82 security issues in gtkwave, all fixed in 3.3.118:

    CVE-2023-32650 CVE-2023-34087 CVE-2023-34436 CVE-2023-35004
    CVE-2023-35057 CVE-2023-35128 CVE-2023-35702 CVE-2023-35703
    CVE-2023-35704 CVE-2023-35955 CVE-2023-35956 CVE-2023-35957
    CVE-2023-35958 CVE-2023-35959 CVE-2023-35960 CVE-2023-35961
    CVE-2023-35962 CVE-2023-35963 CVE-2023-35964 CVE-2023-35969
    CVE-2023-35970 CVE-2023-35989 CVE-2023-35992 CVE-2023-35994
    CVE-2023-35995 CVE-2023-35996 CVE-2023-35997 CVE-2023-36746
    CVE-2023-36747 CVE-2023-36861 CVE-2023-36864 CVE-2023-36915
    CVE-2023-36916 CVE-2023-37282 CVE-2023-37416 CVE-2023-37417
    CVE-2023-37418 CVE-2023-37419 CVE-2023-37420 CVE-2023-37442
    CVE-2023-37443 CVE-2023-37444 CVE-2023-37445 CVE-2023-37446
    CVE-2023-37447 CVE-2023-37573 CVE-2023-37574 CVE-2023-37575
    CVE-2023-37576 CVE-2023-37577 CVE-2023-37578 CVE-2023-37921
    CVE-2023-37922 CVE-2023-37923 CVE-2023-38583 CVE-2023-38618
    CVE-2023-38619 CVE-2023-38620 CVE-2023-38621 CVE-2023-38622
    CVE-2023-38623 CVE-2023-38648 CVE-2023-38649 CVE-2023-38650
    CVE-2023-38651 CVE-2023-38652 CVE-2023-38653 CVE-2023-38657
    CVE-2023-39234 CVE-2023-39235 CVE-2023-39270 CVE-2023-39271
    CVE-2023-39272 CVE-2023-39273 CVE-2023-39274 CVE-2023-39275
    CVE-2023-39316 CVE-2023-39317 CVE-2023-39413 CVE-2023-39414
    CVE-2023-39443 CVE-2023-39444

    Let's first fix unstable and then we can simple build 3.3.118
    for stable-security and oldstable-security as well.
    ...

    I looked at it for LTS, and there are at least two issues to consider:


    1. GTK 2 versus GTK 3

    Between bullseye and bookworm the UI switched from GTK 2 to GTK 3.

    The good news is that in buster both versions of 3.3.118 work with a
    small testcase.

    The bad news is that upstream has different tarballs for GTK 2 and GTK 3.


    2. ghwdump moved to ghdl-tools

    The ghwdump tool (and manpage) was dropped in 3.3.110 from the upstream sources, and is now in ghdl-tools.


    My suggestion would be that I do:

    sid:
    3.3.118-0.1 (or 3.3.118-1 if done by a maintainer)

    bookworm:
    3.3.118-0.1~deb12u1

    bullseye:
    3.3.104+really3.3.118-0.1 (GTK 2 and with ghwdump re-added)

    buster:
    3.3.104+really3.3.118-0.1~deb10u1 (or 3.3.98+really3.3.118-0.1)


    Any comments?
    Especially maintainer feedback would be appreciated.


    Cheers,
    Moritz

    cu
    Adrian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sat Mar 23 22:20:01 2024
    Processing control commands:

    tags 1060407 + patch
    Bug #1060407 [src:gtkwave] Multiple security issues
    Added tag(s) patch.
    tags 1060407 + pending
    Bug #1060407 [src:gtkwave] Multiple security issues
    Added tag(s) pending.

    --
    1060407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060407
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Mon Mar 25 22:20:02 2024
    This is a multi-part message in MIME format...

    Your message dated Mon, 25 Mar 2024 21:14:34 +0000
    with message-id <E1roreM-00FPtz-Fl@fasolo.debian.org>
    and subject line Bug#1060407: fixed in gtkwave 3.3.118-0.1
    has caused the Debian Bug report #1060407,
    regarding Multiple security issues
    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.)


    --
    1060407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060407
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 10 Jan 2024 19:36:47 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-9.9 required=4.0 tests=BAYES_00,FROMDEVELOPER,
    RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,
    XMAILER_REPORTBUG autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 474; hammy, 103; neutral, 36; spammy,
    1. spammytokens:0.995-1--unveiled hammytokens:0.000-+--XDebbugsCc,
    0.000-+--X-Debbugs-Cc, 0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug,
    0.000-+--H*RU:inutil.org
    Return-path: <jmm@debian.org>
    Received: from inutil.org ([109.69.64.57]:43368 helo=viruvalge.hosting.plutex.de)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AE
  • From Adrian Bunk@21:1/5 to All on Fri Mar 29 00:10:01 2024
    Hi,

    attached are proposed debdiffs for updating gtkwave to 3.3.118 in {bookworm,bullseye,buster}-security for review for a DSA
    (and as preview for buster).

    General notes:

    As suggested by the security team in #1060407, this is a backport of a
    new upstream version to fix the 82 CVEs.

    I checked a handful CVEs, and they were also present in buster.
    If anyone insists that I check for every single CVE whether it is also
    in buster I can do that, but that would be a lot of work.

    As already mentioned in #1060407, the ghwdump tool (and manpage) was
    dropped in 3.3.110 from the upstream sources, and is now in ghdl-tools.
    For bullseye and buster it is therefore readded.

    As mentioned in #1060407 there are different tarballs for GTK 2 and GTK 3. Looking closer I realized that this is actually one tarball that
    supports GTK 1+2, and one tarball that supports GTK 2+3.
    I did stay at the GTK 1+2 tarball that was already used before
    for bullseye and buster since there was anyway a different upstream
    tarball required for the +really version that is required to avoid
    creating file conflicts with ghwdump when upgrading to bookworm.

    What does the security team consider the best versioning for bullseye?
    In #1060407 I suggested 3.3.104+really3.3.118-0.1, but now I ended up preferring 3.3.104+really3.3.118-0+deb11u1

    debdiffs contain only changes to debian/


    bookworm notes:
    - version 3.3.118-0.1~deb12u1
    - GTK 3, using GTK 2+3 upstream tarball
    - identical file list in the binary package as before
    - no changes in the runtime dependencies
    - the second debdiff contains the diff to the version in sid
    that was backported
    - viewing a VCD file was tested

    bullseye notes:
    - version 3.3.104+really3.3.118-0+deb11u1
    - GTK 2, using GTK 1+2 upstream tarball
    - ghwdump readded
    - identical file list in the binary package as before
    - only diff in the runtime dependencies is from a
    transitional package:
    [-libgdk-pixbuf2.0-0-] {+libgdk-pixbuf-2.0-0+}
    - viewing a VCD file was tested
    - using ghwdump to dump information from a GHW file was tested

    buster notes:
    - version 3.3.98+really3.3.118-0+deb10u1
    - GTK 2, using GTK 1+2 upstream tarball
    - ghwdump readded
    - identical file list in the binary package as before
    - no changes in the runtime dependencies
    - viewing a VCD file was tested
    - using ghwdump to dump information from a GHW file was tested


    cu
    Adrian

    diff -Nru gtkwave-3.3.114/debian/changelog gtkwave-3.3.118/debian/changelog
    --- gtkwave-3.3.114/debian/changelog 2023-01-20 05:01:31.000000000 +0200
    +++ gtkwave-3.3.118/debian/changelog 2024-03-28 08:53:47.000000000 +0200
    @@ -1,3 +1,58 @@
    +gtkwave (3.3.118-0.1~deb12u1) bookworm-security; urgency=medium
    +
    + * Non-maintainer upload.
    + * Rebuild for bookworm-security.
    +
    + -- Adrian Bunk <bunk@debian.org> Thu, 28 Mar 2024 08:53:47 +0200
    +
    +gtkwave (3.3.118-0.1) unstable; urgency=high
    +
    + * Non-maintainer upload.
    + * New upstream release.
    + - Fixes multiple vulnerabilities:
    + CVE-2023-32650, CVE-2023-34087, CVE-2023-34436, CVE-2023-35004,
    + CVE-2023-35057, CVE-2023-35128, CVE-2023-35702, CVE-2023-35703,
    + CVE-2023-35704, CVE-2023-35955, CVE-2023-35956, CVE-2023-35957,
    + CVE-2023-35958, CVE-2023-35959, CVE-2023-35960, CVE-2023-35961,
    + CVE-2023-35962, CVE-2023-35963, CVE-2023-35964, CVE-2023-35969,
    + CVE-2023-35970, CVE-2023-35989, CVE-2023-35992, CVE-2023-35994,
    + CVE-2023-35995, CVE-2023-35996, CVE-2023-35997, CVE-2023-36746
  • From Moritz =?UTF-8?Q?M=C3=BChlenhoff?=@21:1/5 to All on Sun Mar 31 14:00:01 2024
    Hi Adrian,

    attached are proposed debdiffs for updating gtkwave to 3.3.118 in {bookworm,bullseye,buster}-security for review for a DSA
    (and as preview for buster).

    Thanks!

    General notes:

    I checked a handful CVEs, and they were also present in buster.
    If anyone insists that I check for every single CVE whether it is also
    in buster I can do that, but that would be a lot of work.

    Nah, no need.

    As mentioned in #1060407 there are different tarballs for GTK 2 and GTK 3. Looking closer I realized that this is actually one tarball that
    supports GTK 1+2, and one tarball that supports GTK 2+3.
    I did stay at the GTK 1+2 tarball that was already used before
    for bullseye and buster since there was anyway a different upstream
    tarball required for the +really version that is required to avoid
    creating file conflicts with ghwdump when upgrading to bookworm.

    What does the security team consider the best versioning for bullseye?
    In #1060407 I suggested 3.3.104+really3.3.118-0.1, but now I ended up preferring 3.3.104+really3.3.118-0+deb11u1

    That's fine.

    debdiffs contain only changes to debian/

    The bookworm/bullseye debdiffs looks good, please upload to security-master, thanks!

    Note that both need -sa, but dak needs some special attention when
    uploading to security-master. You'll need to wait for the ACCEPTED mail
    before you can upload the next one.

    Cheers,
    Moritz

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sat Apr 6 09:52:28 2024
    This is a multi-part message in MIME format...

    Your message dated Thu, 04 Apr 2024 22:47:08 +0000
    with message-id <E1rsVrQ-00Bx14-RY@fasolo.debian.org>
    and subject line Bug#1060407: fixed in gtkwave 3.3.118-0.1~deb12u1
    has caused the Debian Bug report #1060407,
    regarding Multiple security issues
    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.)


    --
    1060407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060407
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 10 Jan 2024 19:36:47 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-9.9 required=4.0 tests=BAYES_00,FROMDEVELOPER,
    RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,
    XMAILER_REPORTBUG autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 474; hammy, 103; neutral, 36; spammy,
    1. spammytokens:0.995-1--unveiled hammytokens:0.000-+--XDebbugsCc,
    0.000-+--X-Debbugs-Cc, 0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug,
    0.000-+--H*RU:inutil.org
    Return-path: <jmm@debian.org>
    Received: from inutil.org ([109.69.64.57]:43368 helo=viruvalge.hosting.plutex.de)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AE
  • From Debian Bug Tracking System@21:1/5 to All on Sun Apr 7 19:40:01 2024
    This is a multi-part message in MIME format...

    Your message dated Sun, 07 Apr 2024 17:32:30 +0000
    with message-id <E1rtWNa-008Ylf-Ba@fasolo.debian.org>
    and subject line Bug#1060407: fixed in gtkwave 3.3.104+really3.3.118-0+deb11u1 has caused the Debian Bug report #1060407,
    regarding Multiple security issues
    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.)


    --
    1060407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060407
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 10 Jan 2024 19:36:47 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-9.9 required=4.0 tests=BAYES_00,FROMDEVELOPER,
    RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,
    XMAILER_REPORTBUG autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 474; hammy, 103; neutral, 36; spammy,
    1. spammytokens:0.995-1--unveiled hammytokens:0.000-+--XDebbugsCc,
    0.000-+--X-Debbugs-Cc, 0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug,
    0.000-+--H*RU:inutil.org
    Return-path: <jmm@debian.org>
    Received: from inutil.org ([109.69.64.57]:43368 helo=viruvalge.hosting.plutex.de)
    by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AE