dbcve.org
InsightvmApplication · Rapid7

CVE-2024-6504

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-18
Fix available
A fix is available. Upgrade to 6.6.261 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Rapid7 InsightVM Console versions below 6.6.260 suffer from a protection mechanism failure whereby an attacker with network access to the InsightVM Console can cause it to overload or crash by sending repeated invalid REST requests in a short timeframe, to the Console's port 443 causing the console to enter an exception handling logging loop, exhausting the CPU. There is no indication that an attacker can use this method to escalate privilege, acquire unauthorized access to data, or gain control of protected resources. This issue is fixed in version 6.6.261.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Rapid7 InsightVM Console versions below 6.6.260 contain a protection mechanism failure where repeated invalid REST requests to port 443 cause the console to enter an exception handling logging loop, exhausting CPU resources and resulting in denial of service. This is a resource exhaustion vulnerability stemming from improper exception handling in the REST API endpoint.

MitigationUpgrade to InsightVM Console version 6.6.261 or later. As a compensating control, implement rate limiting or web application firewall rules for the Console's API endpoints to limit the impact of repeated invalid requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
InsightvmApplication
Affected:< 6.6.261

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify InsightVM Console installation
    Locate the InsightVM Console installation directory or check running services for InsightVM processes
    Affected if InsightVM Console is installed and running on the system
  2. Determine the installed version
    Access the Console's administration interface or check the installation files to find the exact version number (typically displayed in the UI footer or in version files within the installation directory)
    Affected if The version number cannot be determined or is below 6.6.261
  3. Compare version against affected range
    Compare your identified version to the affected range: versions below 6.6.261 (including all versions up to 6.6.260)
    Affected if Your installed version is less than 6.6.261
  4. Check port 443 accessibility
    Verify that port 443 (HTTPS) is open and the REST API endpoint is accessible from network locations where invalid requests could be sent repeatedly
    Affected if Port 443 is exposed and reachable from untrusted networks without rate limiting

You are affected if InsightVM Console is running with a version below 6.6.261 and port 443 is accessible for REST API requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.6.261 or later
Fixed in 6.6.261
Interim mitigation

Upgrade to InsightVM Console version 6.6.261 or later. As a compensating control, implement rate limiting or web application firewall rules for the Console's API endpoints to limit the impact of repeated invalid requests.

Recommended fix High confidence

6.6.261

  1. Backup the current InsightVM Console configuration and data before initiating the upgrade
  2. Download InsightVM Console version 6.6.261 from the official Rapid7 portal or repository
  3. Stop the InsightVM Console service to prepare for the upgrade
  4. Install or apply the version 6.6.261 update following standard Rapid7 upgrade procedures
  5. Verify the upgrade was successful by checking the console version
  6. Start the InsightVM Console service
  7. Confirm the console is operational and the resource exhaustion vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Insightvm Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6504 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data