Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Enforce Paramiko >= 2.4.2 #853

Merged
merged 1 commit into from
Oct 30, 2018
Merged

Enforce Paramiko >= 2.4.2 #853

merged 1 commit into from
Oct 30, 2018

Conversation

mirceaulinic
Copy link
Member

This is due to CVE-2018-7750 and CVE-2018-1000805, and the underlying libraries may not have this requirement.

See https://nvd.nist.gov/vuln/detail/CVE-2018-7750 and https://nvd.nist.gov/vuln/detail/CVE-2018-1000805 for further details.

@mirceaulinic mirceaulinic added this to the 2.3.4 milestone Oct 30, 2018
@mirceaulinic
Enforce Paramiko >= 2.4.2
546b32e 
This is due to CVE-2018-7750 and CVE-2018-1000805, and the underlying libraries may not have this requirement.

See https://nvd.nist.gov/vuln/detail/CVE-2018-7750 and https://nvd.nist.gov/vuln/detail/CVE-2018-1000805 for further details.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 80.384% when pulling 546b32e on modern-paramiko into 64f04f4 on develop.

3 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 80.384% when pulling 546b32e on modern-paramiko into 64f04f4 on develop.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 80.384% when pulling 546b32e on modern-paramiko into 64f04f4 on develop.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 80.384% when pulling 546b32e on modern-paramiko into 64f04f4 on develop.

@coveralls
Copy link

coveralls commented Oct 30, 2018 •
edited
Loading

Coverage Status

Coverage remained the same at 80.384% when pulling 546b32e on modern-paramiko into 64f04f4 on develop.

ktbyers
ktbyers approved these changes Oct 30, 2018
View reviewed changes
Copy link
Contributor

@ktbyers ktbyers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note, this is not a real issue for napalm/netmiko since we aren't using Paramiko in server mode. But fix anyways so GitHub stops nagging us about it.

@ktbyers ktbyers merged commit c0772ad into develop Oct 30, 2018
@ktbyers ktbyers deleted the modern-paramiko branch December 13, 2018 03:10
ExaneServerTeam pushed a commit to ExaneServerTeam/napalm that referenced this pull request Mar 6, 2020
@mirceaulinic @ExaneServerTeam
Enforce Paramiko >= 2.4.2 (napalm-automation#853)
3e2dcad 
This is due to CVE-2018-7750 and CVE-2018-1000805, and the underlying libraries may not have this requirement.

See https://nvd.nist.gov/vuln/detail/CVE-2018-7750 and https://nvd.nist.gov/vuln/detail/CVE-2018-1000805 for further details.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ktbyers ktbyers ktbyers approved these changes

@dbarrosop dbarrosop Awaiting requested review from dbarrosop

Assignees
No one assigned
Labels
cve
Projects
None yet
Milestone
2.3.4
Development

Successfully merging this pull request may close these issues.
3 participants
@mirceaulinic @coveralls @ktbyers