CVE-2017-5243
First published: Tue Jun 06 2017(Updated: )
The default SSH configuration in Rapid7 Nexpose hardware appliances shipped before June 2017 does not specify desired algorithms for key exchange and other important functions. As a result, it falls back to allowing ALL algorithms supported by the relevant version of OpenSSH and makes the installations vulnerable to a range of MITM, downgrade, and decryption attacks.
Credit: cve@rapid7.con
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Rapid7 Nexpose | <=6.4.40 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2017-5243?
CVE-2017-5243 is considered a medium severity vulnerability due to its potential exploitation via insecure algorithms.
How do I fix CVE-2017-5243?
To fix CVE-2017-5243, update your Rapid7 Nexpose appliance to a version later than June 2017, ensuring secure algorithms are specified.
What are the risks associated with CVE-2017-5243?
The risks associated with CVE-2017-5243 include unauthorized access and potential data breaches due to weak SSH configurations.
Which versions of Rapid7 Nexpose are affected by CVE-2017-5243?
CVE-2017-5243 affects Rapid7 Nexpose versions up to and including 6.4.40.
Is there a workaround for CVE-2017-5243?
A temporary workaround for CVE-2017-5243 is to manually configure the SSH settings to enforce stronger key exchange algorithms.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/weakness
- agent/severity
- agent/references
- agent/event
- agent/first-publish-date
- agent/tags
- agent/description
- agent/source
- vendor/rapid7
- canonical/rapid7 nexpose
- version/rapid7 nexpose/6.4.40