CVE-2019-5631
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 · uneditedThe Rapid7 InsightAppSec broker suffers from a DLL injection vulnerability in the 'prunsrv.exe' component of the product. If exploited, a local user of the system (who must already be authenticated to the operating system) can elevate their privileges with this vulnerability to the privilege level of InsightAppSec (usually, SYSTEM). This issue affects version 2019.06.24 and prior versions of the product.
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 InsightAppSec contains a DLL injection vulnerability in the prunsrv.exe service component. A local authenticated user can exploit this to inject a malicious DLL and escalate privileges to SYSTEM level, as the service runs with elevated privileges.
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<= 2019.06.24CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Check if Rapid7 InsightAppSec is installedLook for InsightAppSec installation directories or check installed programs list for 'InsightAppSec' or 'Rapid7 InsightAppSec'Affected if InsightAppSec is present on the system
-
Determine the installed InsightAppSec versionCheck the version of the installed InsightAppSec software, typically found in the application directory, about dialog, or uninstall entryAffected if Version is 2019.06.24 or earlier (any version <= 2019.06.24)
-
Locate the prunsrv.exe service componentFind prunsrv.exe in the InsightAppSec installation directory, which is the service component referenced in the vulnerabilityAffected if prunsrv.exe exists in the InsightAppSec installation folder
-
Verify the prunsrv.exe service is installed and runningCheck Windows Services for a service associated with InsightAppSec that uses prunsrv.exe, or check if prunsrv.exe process is running with elevated privilegesAffected if The service runs with SYSTEM or elevated privileges and is accessible to local authenticated users
-
Check service binary permissionsInspect file permissions on the prunsrv.exe binary to determine if a local authenticated user can modify or replace itAffected if Non-admin users have write or modify permissions to the prunsrv.exe binary or its directory
The system is affected if InsightAppSec version 2019.06.24 or earlier is installed with the prunsrv.exe service running with elevated privileges and accessible to local 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.
From vendor dataUpdate InsightAppSec to a version newer than 2019.06.24. As an interim measure, restrict physical access to the system and monitor for unauthorized modifications to the service binary.
- Consultation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5631 — 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-5631 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