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

Le 30/12/2023 à 21:13, Salvatore Bonaccorso a écrit :

Groovy support was introduced in JLine 3.14.0 [1], so our old 3.3.1
version is not affected by CVE-2023-50572.

Emmanuel Bourg

[1] https://github.com/jline/jline3/commit/5e0eb5e2

Hi Emmanuel,

Thanks, I have updated the security-tracker information.

Regards,
Salvatore