Homepage

ipython@0.11 vulnerabilities

IPython: Productive Interactive Computing

  • latest version

    8.30.0

  • latest non vulnerable version

    8.30.0

  • first published

    17 years ago

  • latest version published

    17 days ago

  • licenses detected

  • View ipython package health on Snyk Advisor  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the ipython package. This does not include vulnerabilities belonging to this package’s dependencies.

    How to fix?

    Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Remote Code Execution (RCE)

    Affected versions of this package are vulnerable to Remote Code Execution (RCE) with very specific prerequisites.

    This vulnerability requires that the function IPython.utils.terminal.set_term_title be called on Windows in a Python environment where ctypes is not available. The dependency on ctypes in IPython.utils._process_win32 prevents the vulnerable code from ever being reached in the ipython binary.

    However, as a library that could be used by another tool set_term_title could be called and hence introduce a vulnerability. Should an attacker get untrusted input to an instance of this function they would be able to inject shell commands as current process and limited to the scope of the current process. Users of ipython as a library are advised to upgrade. Users unable to upgrade should ensure that any calls to the IPython.utils.terminal.set_term_title function are done with trusted or filtered input.

    How to fix Remote Code Execution (RCE)?

    Upgrade ipython to version 8.10.0 or higher.

    [,8.10.0)
    • H
    Arbitrary Code Execution

    Affected versions of this package are vulnerable to Arbitrary Code Execution by not properly managing cross-user temporary files. This vulnerability allows one user to run code as another on the same machine.

    How to fix Arbitrary Code Execution?

    Upgrade ipython to version 7.16.3, 7.31.1, 8.0.1 or higher.

    [,7.16.3)[7.17.0,7.31.1)[8.0.0,8.0.1)
    • M
    Arbitrary Code Execution

    Affected versions of ipython are vulnerable to Arbitrary Code Executionhttps://nvd.nist.gov/vuln/detail/CVE-2015-7337.

    The editor in IPython Notebook before 3.2.2 and Jupyter Notebook 4.0.x before 4.0.5 allows remote attackers to execute arbitrary JavaScript code via a crafted file, which triggers a redirect to files/, related to MIME types.

    How to fix Arbitrary Code Execution?

    Upgrade ipython to version 3.2.2 or higher.

    [,3.2.2)
    • M
    Cross-site Scripting (XSS)

    Affected versions of ipython are vulnerable to Cross-Site Scripting (XSS) attacks.

    Cross-site scripting (XSS) vulnerability in the file browser in notebook/notebookapp.py in IPython Notebook before 3.2.2 and Jupyter Notebook 4.0.x before 4.0.5 allows remote attackers to inject arbitrary web script or HTML via a folder name. NOTE: this was originally reported as a cross-site request forgery (CSRF) vulnerability, but this may be inaccurate.

    How to fix Cross-site Scripting (XSS)?

    Upgrade ipython to version 3.2.2 or higher.

    [,3.2.2)
    • H
    Cross-site Request Forgery (CSRF)

    ipython is a Productive Interactive Computing.

    Affected versions of this package are vulnerable to Cross-site Request Forgery (CSRF) attacks.

    [,3.2.1)
    • M
    Cross-site Scripting (XSS)

    ipython is a Productive Interactive Computing.

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks.

    [,3.2.0)
    • M
    Cross-site Scripting (XSS)

    ipython is a Productive Interactive Computing.

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS) attacks.

    [,3.2.0)
    Go back to all versions of this package