CVE-2022-3913: Rapid7 Nexpose Certificate Validation Issue
First published: Wed Feb 01 2023(Updated: )
Rapid7 Nexpose and InsightVM versions 6.6.82 through 6.6.177 fail to validate the certificate of the update server when downloading updates. This failure could allow an attacker in a privileged position on the network to provide their own HTTPS endpoint, or intercept communications to the legitimate endpoint. The attacker would need some pre-existing access to at least one node on the network path between the Rapid7-controlled update server and the Nexpose/InsightVM application, and the ability to either spoof the update server's FQDN or redirect legitimate traffic to the attacker's server in order to exploit this vulnerability. Note that even in this scenario, an attacker could not normally replace an update package with a malicious package, since the update process validates a separate, code-signing certificate, distinct from the HTTPS certificate used for communication. This issue was resolved on February 1, 2023 in update 6.6.178 of Nexpose and InsightVM.
Credit: cve@rapid7.con
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Rapid7 Nexpose | >=6.6.82<6.6.178 |
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.
Reference Links
Frequently Asked Questions
What is CVE-2022-3913?
CVE-2022-3913 is a vulnerability in Rapid7 Nexpose and InsightVM versions 6.6.82 through 6.6.177 that allows an attacker to provide their own HTTPS endpoint or intercept communication by failing to validate the certificate of the update server.
What is the severity of CVE-2022-3913?
The severity of CVE-2022-3913 is medium with a severity value of 5.3.
How does CVE-2022-3913 affect Rapid7 Nexpose and InsightVM?
CVE-2022-3913 affects Rapid7 Nexpose and InsightVM versions 6.6.82 through 6.6.177 by failing to validate the certificate of the update server when downloading updates.
How can an attacker exploit CVE-2022-3913?
An attacker in a privileged position on the network can exploit CVE-2022-3913 by providing their own HTTPS endpoint or intercepting communications to the legitimate update server.
Is there a fix for CVE-2022-3913?
Yes, Rapid7 has released a fix for CVE-2022-3913. It is recommended to update to version 6.6.178 or later of Rapid7 Nexpose and InsightVM to mitigate the vulnerability.
- collector/nvd-index
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/title
- agent/last-modified-date
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/description
- agent/weakness
- agent/event
- agent/first-publish-date
- vendor/rapid7
- canonical/rapid7 nexpose
- version/rapid7 nexpose/6.6.82