CVE-2015-8264
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 · uneditedUntrusted search path vulnerability in F-Secure Online Scanner allows remote attackers to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse DLL that is located in the same folder as F-SecureOnlineScanner.exe.
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 confidenceF-Secure Online Scanner has an untrusted search path vulnerability that allows DLL hijacking. The application loads DLLs from its current working directory without validating the path, enabling an attacker to place a malicious DLL in the same folder as F-SecureOnlineScanner.exe to achieve arbitrary code execution.
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 dataall versionsCVSS 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.
-
Locate F-Secure Online Scanner installationSearch for F-SecureOnlineScanner.exe in common installation directories (C:\Program Files\F-Secure, C:\Program Files (x86)\F-Secure) or use 'where F-SecureOnlineScanner.exe' commandAffected if F-SecureOnlineScanner.exe exists on the system
-
Identify current working directory usageCheck the directory from which F-Secure Online Scanner is typically launched. Look for shortcuts, start menu entries, or scheduled tasks that specify a working directory using 'Start in' fieldAffected if The application launches from a directory writable by standard users (e.g., Downloads, Desktop, or a shared network folder)
-
Check for vulnerable DLL locationsExamine the application directory for world-writable locations where an unprivileged user could drop a malicious DLL. Look for directories with weak permissions (Everyone, Users, or Authenticated Users with Write/modify access)Affected if The F-Secure Online Scanner directory or its launch directory allows standard users to create or modify files
-
Verify DLL search behaviorUse Process Monitor (procmon) from Sysinternals to monitor F-SecureOnlineScanner.exe for DLL load events, specifically looking for loads from the current working directory rather than system pathsAffected if The application loads DLLs from its launch directory instead of secure system directories
A user is affected if F-Secure Online Scanner runs from or can be launched by an attacker from a directory where that attacker can place a malicious DLL.
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 dataFix the DLL loading mechanism to use absolute paths or secure DLL search order (e.g., Safe DLL Search Mode), ensuring the application only loads DLLs from trusted system directories.
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8264 — 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-2015-8264 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