CVE-2017-5236
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 · uneditedEditions of Rapid7 AppSpider Pro installers prior to version 6.14.060 contain a DLL preloading vulnerability, wherein it is possible for the installer to load a malicious DLL located in the current working directory of the installer.
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 confidenceThis is a DLL preloading vulnerability in Rapid7 AppSpider Pro installers prior to version 6.14.060. The installer loads DLLs from the current working directory before checking system paths, allowing an attacker to place a malicious DLL with an expected name to achieve arbitrary code execution during the installation process.
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.14.059CVSS 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.0/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.
-
Find installed AppSpider Pro versionOpen Windows Control Panel > Programs and Features, locate 'Rapid7 AppSpider Pro' in the list, and note the version columnAffected if Version listed is 6.14.059 or lower
-
Check executable version propertyNavigate to the AppSpider Pro installation directory (commonly C:\Program Files\Rapid7\AppSpider Pro), right-click the main executable (often AppSpider.exe or similar), select Properties, and view the File Version on the Details tabAffected if File version shows 6.14.059 or lower
-
Query version from Windows RegistryOpen regedit and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AppSpider Pro GUID} or look under HKLM\SOFTWARE\Rapid7\AppSpider Pro for a Version valueAffected if Registry Version value is 6.14.059 or lower or entry is missing (indicating very old install)
-
Verify installer version if availableIf the original installer MSI or EXE is available, right-click it, select Properties, and check the Details tab for Product Version or File VersionAffected if Installer version is 6.14.059 or lower
You are affected if any installed AppSpider Pro version or installer version is 6.14.059 or lower, as this version range contains the vulnerable DLL preloading installer logic.
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 dataUpgrade to AppSpider Pro version 6.14.060 or later, which contains the patched installer. Verify installer integrity before running.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2017-5236 — 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-2017-5236 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