CVE-2018-1000805: High severity Paramiko Paramiko vulnerability

Published Oct 8, 2018
·
Updated

Last updated 25 August 2025

Other sources

Paramiko version 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5, 1.17.6 contains a Incorrect Access Control vulnerability in SSH server that can result in RCE. This attack appear to be exploitable via network connectivity.

— Launchpad

Python Paramiko through versions 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5 and 1.17.6 is vulnerable to an authentication bypass in paramiko/authhandler.py. A remote attacker could exploit this vulnerability in paramiko SSH servers to execute arbitrary code.

Upstream Issue:

https://github.com/paramiko/paramiko/issues/1283

Upstream Patch:

https://github.com/paramiko/paramiko/commit/56c96a65

— Red Hat

Affected Software

58 affected componentsFixes available
redhat/python-paramiko<2.4.2
2.4.2
redhat/python-paramiko<2.3.3
2.3.3
redhat/python-paramiko<2.2.4
2.2.4
redhat/python-paramiko<2.1.6
2.1.6
redhat/python-paramiko<2.0.9
2.0.9
pip/paramiko>=1.5.1<2.0.9
2.0.9
pip/paramiko>=2.1.0<2.1.6
2.1.6
pip/paramiko>=2.2.0<2.2.4
2.2.4
pip/paramiko>=2.3.0<2.3.3
2.3.3
pip/paramiko>=2.4.0<2.4.2
2.4.2
Paramiko Paramiko=1.17.6
Paramiko Paramiko=1.18.5
Paramiko Paramiko=2.0.8
Paramiko Paramiko=2.1.5
Paramiko Paramiko=2.2.3
Paramiko Paramiko=2.3.2
Paramiko Paramiko=2.4.1
redhat Ansible Tower=3.3
redhat Virtualization Host=4.0
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=6.4
redhat Enterprise Linux Server Aus=6.5
redhat Enterprise Linux Server Aus=6.6
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Eus=6.7
redhat Enterprise Linux Server Eus=7.6
redhat Enterprise Linux Server Tus=6.6
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Workstation=6.0
redhat Enterprise Linux Workstation=7.0
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=18.10
debian/paramiko
2.7.2-12.7.2-1+deb11u12.12.0-23.5.1-34.0.0-14.0.0-2
alpine/py-paramiko<2.1.6-r0
2.1.6-r0
alpine/py-paramiko<2.4.2-r0
2.4.2-r0
alpine/py-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0
alpine/py3-paramiko<2.4.2-r0
2.4.2-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/python-paramiko to a version that resolves this vulnerability.

    Fixed in 2.4.2
  2. Upgrade

    Upgrade redhat/python-paramiko to a version that resolves this vulnerability.

    Fixed in 2.3.3
  3. Upgrade

    Upgrade redhat/python-paramiko to a version that resolves this vulnerability.

    Fixed in 2.2.4
  4. Upgrade

    Upgrade redhat/python-paramiko to a version that resolves this vulnerability.

    Fixed in 2.1.6
  5. Upgrade

    Upgrade redhat/python-paramiko to a version that resolves this vulnerability.

    Fixed in 2.0.9
  6. Upgrade

    Upgrade pip/paramiko to a version that resolves this vulnerability.

    Fixed in 2.0.9
  7. Upgrade

    Upgrade pip/paramiko to a version that resolves this vulnerability.

    Fixed in 2.1.6
  8. Upgrade

    Upgrade pip/paramiko to a version that resolves this vulnerability.

    Fixed in 2.2.4
  9. Upgrade

    Upgrade pip/paramiko to a version that resolves this vulnerability.

    Fixed in 2.3.3
  10. Upgrade

    Upgrade pip/paramiko to a version that resolves this vulnerability.

    Fixed in 2.4.2
  11. Upgrade

    Upgrade debian/paramiko to a version that resolves this vulnerability.

    Fixed in 2.7.2-1Fixed in 2.7.2-1+deb11u1Fixed in 2.12.0-2Fixed in 3.5.1-3Fixed in 4.0.0-1Fixed in 4.0.0-2
  12. Upgrade

    Upgrade alpine/py-paramiko to a version that resolves this vulnerability.

    Fixed in 2.1.6-r0
  13. Upgrade

    Upgrade alpine/py-paramiko to a version that resolves this vulnerability.

    Fixed in 2.4.2-r0
  14. Upgrade

    Upgrade alpine/py3-paramiko to a version that resolves this vulnerability.

    Fixed in 2.4.2-r0

Event History

Oct 8, 2018
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Data Sourced
via NVD·03:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·03:29 PM
DescriptionSeverityAffected Software
Oct 10, 2018
Advisory Published
via GitHub·04:10 PM

Frequently Asked Questions

1

What is the vulnerability ID?

The vulnerability ID is CVE-2018-1000805.

2

What is the severity of CVE-2018-1000805?

The severity of CVE-2018-1000805 is high with a severity value of 8.8.

3

What is the affected software?

The affected software is Paramiko versions 2.4.1, 2.3.2, 2.2.3, 2.1.5, 2.0.8, 1.18.5, and 1.17.6.

4

What is the impact of CVE-2018-1000805?

The impact of CVE-2018-1000805 is remote code execution (RCE).

5

How can I fix CVE-2018-1000805?

To fix CVE-2018-1000805, update Paramiko to version 2.4.2 or higher.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203