Debian Bug report logs -
#1057454
jupyter-server: CVE-2023-49080: Server errors include tracebacks with path information
Reply or subscribe to this bug.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, carnil@debian.org, team@security.debian.org, Debian Python Team <team+python@tracker.debian.org>
:
Bug#1057454
; Package src:jupyter-server
.
(Tue, 05 Dec 2023 11:03:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Salvatore Bonaccorso <carnil@debian.org>
:
New Bug report received and forwarded. Copy sent to carnil@debian.org, team@security.debian.org, Debian Python Team <team+python@tracker.debian.org>
.
(Tue, 05 Dec 2023 11:03:03 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Source: jupyter-server
Version: 1.23.3-1
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 jupyter-server.
CVE-2023-49080[0]:
| The Jupyter Server provides the backend (i.e. the core services,
| APIs, and REST endpoints) for Jupyter web applications like Jupyter
| notebook, JupyterLab, and Voila. Unhandled errors in API requests
| coming from an authenticated user include traceback information,
| which can include path information. There is no known mechanism by
| which to trigger these errors without authentication, so the paths
| revealed are not considered particularly sensitive, given that the
| requesting user has arbitrary execution permissions already in the
| same environment. A fix has been introduced in commit `0056c3aa52`
| which no longer includes traceback information in JSON error
| responses. For compatibility, the traceback field is present, but
| always empty. This commit has been included in version 2.11.2. Users
| are advised to upgrade. There are no known workarounds for this
| vulnerability.
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-49080
https://www.cve.org/CVERecord?id=CVE-2023-49080
[1] https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-h56g-gq9v-vc8r
[2] https://github.com/jupyter-server/jupyter_server/commit/0056c3aa52cbb28b263a7a609ae5f17618b36652
Please adjust the affected versions in the BTS as needed.
Regards,
Salvatore
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian Python Team <team+python@tracker.debian.org>
:
Bug#1057454
; Package src:jupyter-server
.
(Tue, 05 Dec 2023 11:18:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Salvatore Bonaccorso <carnil@debian.org>
:
Extra info received and forwarded to list. Copy sent to Debian Python Team <team+python@tracker.debian.org>
.
(Tue, 05 Dec 2023 11:18:02 GMT) (full text, mbox, link).
Message #10 received at 1057454@bugs.debian.org (full text, mbox, reply):
Control: severity -1 normal
On Tue, Dec 05, 2023 at 11:58:24AM +0100, Salvatore Bonaccorso wrote:
> Source: jupyter-server
> Version: 1.23.3-1
> 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 jupyter-server.
>
> CVE-2023-49080[0]:
> | The Jupyter Server provides the backend (i.e. the core services,
> | APIs, and REST endpoints) for Jupyter web applications like Jupyter
> | notebook, JupyterLab, and Voila. Unhandled errors in API requests
> | coming from an authenticated user include traceback information,
> | which can include path information. There is no known mechanism by
> | which to trigger these errors without authentication, so the paths
> | revealed are not considered particularly sensitive, given that the
> | requesting user has arbitrary execution permissions already in the
> | same environment. A fix has been introduced in commit `0056c3aa52`
> | which no longer includes traceback information in JSON error
> | responses. For compatibility, the traceback field is present, but
> | always empty. This commit has been included in version 2.11.2. Users
> | are advised to upgrade. There are no known workarounds for this
> | vulnerability.
As disclosure of path information has not really a security impact in
Debian, downgrading the severity further.
Regards,
Salvatore
Severity set to 'normal' from 'important'
Request was from Salvatore Bonaccorso <carnil@debian.org>
to 1057454-submit@bugs.debian.org
.
(Tue, 05 Dec 2023 11:18:02 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Wed Dec 6 08:17:20 2023;
Machine Name:
buxtehude
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.