CVE-2022-4261 json
Rapid7 Nexpose Update Validation Issue
published 2022-12-07 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-51617
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
Rapid7 Nexpose and InsightVM versions prior to 6.6.172 failed to reliably validate the authenticity of update contents. This failure could allow an attacker to provide a malicious update and alter the functionality of Rapid7 Nexpose. The attacker would need some pre-existing mechanism to provide a malicious update, either through a social engineering effort, privileged access to replace downloaded updates in transit, or by performing an Attacker-in-the-Middle attack on the update service itself.
Patch / fix
- rapid7 insightvm 6.6.172
- rapid7 nexpose 6.6.172
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- rapid7.com https://www.rapid7.com/blog/post/2022/12/7/cve-2022-4261-rapid7-nexpose-update-validation-issue-fixed referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Rapid7 Nexpose
- Rapid7 InsightVM
Classification
- Weakness
-
- CWE-494 Download of Code Without Integrity Check
References
-
rapid7.com
/blog/post/2022/12/7/cve-2022-4261-rapid7-nexpose-update-validation-issue-fixed
exploit, mitigation, vendor-advisory
-
docs.rapid7.com
/release-notes/nexpose/20221207/
release-notes, vendor-advisory
-
docs.rapid7.com
/release-notes/insightvm/20221207/
release-notes, vendor-advisory
Sources
- CVE List CVE-2022-4261
- NVD CVE-2022-4261
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.