CVE-2017-5240
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 prior to version 6.14.060 contain a heap-based buffer overflow in the FLAnalyzer.exe component. A malicious or malformed Flash source file can cause a denial of service condition when parsed by this component, causing the application to crash.
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 AppSpider Pro versions prior to 6.14.060 contain a heap-based buffer overflow vulnerability in the FLAnalyzer.exe component used for Flash file analysis. When parsing a malicious or malformed Flash source file, the application fails to properly validate buffer boundaries, leading to heap corruption and subsequent denial of service through application crash.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Verify AppSpider Pro is installedCheck for AppSpider Pro installation directory, typically in C:\Program Files\Rapid7\AppSpider\ or look in Windows Add/Remove ProgramsAffected if AppSpider Pro is not installed on the system
-
Identify the installed AppSpider Pro versionCheck the version of AppSpider Pro by right-clicking the executable (often AppSpider.exe or within the installation directory), or look at the program's properties in Add/Remove Programs. The version is displayed as major.minor.build (e.g., 6.14.059)Affected if The version number is 6.14.059 or lower (e.g., 6.14.058, 6.14.050, etc.)
-
Confirm FLAnalyzer.exe component is presentNavigate to the AppSpider Pro installation directory and search for FLAnalyzer.exe, or check common subdirectories like \bin\ or \tools\Affected if FLAnalyzer.exe exists in the installation directory, indicating the Flash analysis component is installed
-
Check if Flash file analysis is enabledReview AppSpider Pro configuration settings, scan profiles, or policy files to determine whether FLAnalyzer is actively enabled for scanning operationsAffected if FLAnalyzer is enabled and configured to process Flash content as part of scans
A user is affected if AppSpider Pro version 6.14.059 or lower is installed, FLAnalyzer.exe is present, and Flash file analysis features are enabled to process untrusted Flash files.
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 AppSpider Pro to version 6.14.060 or later to obtain the vendor patch. Until upgrade is complete, disable or avoid analyzing untrusted Flash files with the FLAnalyzer component.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5240 — 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-5240 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