[From nobody Tue Nov  3 00:21:06 2026
Received: (at submit) by bugs.debian.org; 30 Dec 2023 20:13:42 +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.8 required=4.0 tests=BAYES_00,FROMDEVELOPER,
 KHOP_HELO_FCRDNS,MD5_SHA1_SUM,RDNS_DYNAMIC,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, 27; hammy, 149; neutral, 55; spammy,
 1. spammytokens:0.945-+--H*r:bugs.debian.org
 hammytokens:0.000-+--H*F:U*carnil, 0.000-+--XDebbugsCc,
 0.000-+--X-Debbugs-Cc, 0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug
Return-path: <carnil@debian.org>
Received: from c-82-192-242-114.customer.ggaweb.ch ([82.192.242.114]:35092
 helo=eldamar.lan) by buxtehude.debian.org with esmtp (Exim 4.94.2)
 (envelope-from <carnil@debian.org>) id 1rJfiH-00H4sR-4B
 for submit@bugs.debian.org; Sat, 30 Dec 2023 20:13:42 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso <carnil@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: jline3: CVE-2023-50572
Message-ID: <170396721687.1585634.17910989852659455048.reportbug@eldamar.lan>
X-Mailer: reportbug 12.0.0
Date: Sat, 30 Dec 2023 21:13:36 +0100
Delivered-To: submit@bugs.debian.org

Source: jline3
Version: 3.3.1-3
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerability was published for jline3.

CVE-2023-50572[0]:
| An issue in the component GroovyEngine.execute of jline-groovy
| v3.24.1 allows attackers to cause an OOM (OutofMemory) error.

Now I'm not completely sure about the assessment. The code in 3.3.1
got some refactoring in laeter version and the upstream commit from
3.25.0 fixing the issue would not apply cleanly, but I'm not 100%
convinced htat the issue is only introduced later. Please double check
that. In case not, where was the issue introduced, can we pin-point
that?

Additionally, in case the above is asserted to be correct, are the
older series 2.x and 1.x as well affected?


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-50572
    https://www.cve.org/CVERecord?id=CVE-2023-50572
[1] https://github.com/jline/jline3/commit/f3c60a3e6255e8e0c20d5043a4fe248446f292bb
[2] https://github.com/jline/jline3/issues/909

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]