CVE-2023-0681
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 · uneditedRapid7 InsightVM versions 6.6.178 and lower suffers from an open redirect vulnerability, whereby an attacker has the ability to redirect the user to a site of the attacker’s choice using the ‘page’ parameter of the ‘data/console/redirect’ component of the application. This issue was resolved in the February, 2023 release of version 6.6.179.
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 confidenceRapid7 InsightVM versions 6.6.178 and below contains an open redirect vulnerability in the 'data/console/redirect' component. The 'page' parameter accepts arbitrary URLs, allowing attackers to redirect users to malicious sites via a trusted application URL.
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< 6.6.179CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify InsightVM versionLog into the InsightVM console and navigate to the Administration or About section to view the product version. Alternatively, check the version via the API endpoint /api/3/about or inspect the installer/VM files if accessing the backend.Affected if The displayed version is 6.6.178 or below (any version lower than 6.6.179)
-
Confirm console web interface is accessibleVerify that the InsightVM web console is accessible to users. The vulnerable component resides in the data/console/redirect path.Affected if The web interface is exposed and users can access the application login page
-
Check for vulnerable redirect endpointInspect the application's URL structure and confirm the /data/console/redirect endpoint exists. This endpoint accepts a 'page' parameter.Affected if The endpoint /data/console/redirect is present and the 'page' parameter can be manipulated with arbitrary URLs
-
Test for open redirect behavior (optional validation)If authorized, submit a request to /data/console/redirect?page=https://example.com and verify the application performs a redirect to the provided URL instead of validating against an allowlist.Affected if The application redirects to arbitrary external domains without validation
You are affected if InsightVM version is 6.6.178 or below and the web console with the vulnerable /data/console/redirect endpoint is accessible to users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.6.179
Upgrade to InsightVM version 6.6.179 or higher (February 2023 release) to remediate this vulnerability.
6.6.179 (February 2023 release) or later
- Ensure you have a complete backup of your InsightVM database and configuration before upgrading.
- Download InsightVM version 6.6.179 or later from the Rapid7 customer portal.
- Follow the standard InsightVM upgrade procedure: stop the InsightVM services, run the upgrade installer, and verify the installation completes successfully.
- Restart the InsightVM services and verify the console is accessible.
- Confirm the vulnerability is resolved by checking that the 'data/console/redirect' component no longer allows arbitrary URL redirection via the 'page' parameter.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0681 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-0681 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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