CVE-2019-5640
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 Nexpose versions prior to 6.6.114 suffer from an information exposure issue whereby, when the user's session has ended due to inactivity, an attacker can use the inspect element browser feature to remove the login panel and view the details available in the last webpage visited by previous user
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 confidenceIn Nexpose versions prior to 6.6.114, when a user's session times out due to inactivity, the login panel is displayed as an overlay without properly clearing the underlying page content from the DOM. An attacker with access to the browser can use developer tools to remove the login overlay and view sensitive details from the last webpage visited by the previous user.
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.114CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Nexpose versionLocate the Nexpose instance and check its version number, typically found in the product UI (Help > About) or in version configuration filesAffected if Version is shown as lower than 6.6.114
-
Confirm product is Rapid7 NexposeVerify the affected product is Rapid7 Nexpose (not another Rapid7 product)Affected if Product is Rapid7 Nexpose and version is below 6.6.114
-
Test session timeout behaviorLog into Nexpose, navigate to a page containing data, wait for session to timeout or manually trigger timeout, then use browser developer tools to inspect whether the previous page content remains in the DOM beneath the login overlayAffected if After session timeout, the login overlay appears but the underlying page DOM elements remain accessible and visible when the overlay is removed via developer tools
You are affected if running Rapid7 Nexpose version lower than 6.6.114 and session timeout leaves previous page content accessible in the DOM.
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.114
Upgrade to Nexpose version 6.6.114 or later, which implements proper session termination that securely clears or removes previous page content from the client-side when the session ends.
6.6.114
- Verify current Nexpose version by accessing the Nexpose console and checking the product version
- Download Nexpose version 6.6.114 or later from the Rapid7 customer portal at https://www.rapid7.com/products/nexpose/download/
- Follow standard Nexpose upgrade procedures: stop the Nexpose service, run the installer for the new version, and complete the upgrade wizard
- After upgrade, restart the Nexpose service
- Verify the upgrade was successful by checking the console shows version 6.6.114 or later
- Test that the login session timeout now properly clears cached page content
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5640 — 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-2019-5640 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