CVE-2019-5638
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 6.5.50 and prior suffer from insufficient session expiration when an administrator performs a security relevant edit on an existing, logged on user. For example, if a user's password is changed by an administrator due to an otherwise unrelated credential leak, that user account's current session is still valid after the password change, potentially allowing the attacker who originally compromised the credential to remain logged in and able to cause further damage.
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 Nexpose versions 6.5.50 and prior fail to invalidate active user sessions when an administrator performs security-relevant edits such as password changes. When an administrator changes a user's password (e.g., in response to a credential leak), the affected user's existing session remains valid, allowing an attacker who compromised the original credentials to continue operating within the application.
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.5.50CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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 if Rapid7 Nexpose is installedLocate Nexpose installation directories or check system services for 'nexpose' or 'InsightVM' processesAffected if Rapid7 Nexpose is found on the system
-
Determine the installed Nexpose versionRun 'nexpose-cli -v' or check the version file in the installation directory (typically in <install_path>/nsc/nse.xml or similar version manifest)Affected if Version cannot be determined or is 6.5.50 or lower
-
Compare version against affected rangeReview the discovered version number against the vulnerable range: any version <= 6.5.50 is affectedAffected if Installed version is 6.5.50 or any lower version number
-
Review session activity logsExamine Nexpose audit and session logs for concurrent sessions belonging to users whose passwords were changedAffected if Active sessions exist for users after their passwords were modified by an administrator
The environment is affected if Rapid7 Nexpose version 6.5.50 or prior is installed, as the password change feature fails to invalidate existing user sessions.
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.
From vendor dataOrganizations should monitor for unauthorized session activity, manually terminate active sessions for users whose credentials have been changed, and apply vendor patches when available. Until the vendor releases a fix, implement strict session monitoring and consider enforcing periodic re-authentication.
- Consultation4.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 $1,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5638 — 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-5638 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