Information Exposure Affecting jupyter-server package, versions *


Severity

Recommended
low

Based on Debian security rating.

Threat Intelligence

EPSS
0.08% (36th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN11-JUPYTERSERVER-6099133
  • published5 Dec 2023
  • disclosed4 Dec 2023

Introduced: 4 Dec 2023

CVE-2023-49080  (opens in a new tab)
CWE-209  (opens in a new tab)

How to fix?

There is no fixed version for Debian:11 jupyter-server.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jupyter-server package and not the jupyter-server package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

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.

CVSS Scores

version 3.1