CVE-2015-2264
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 · uneditedMultiple untrusted search path vulnerabilities in (1) EQATEC.Analytics.Monitor.Win32_vc100.dll and (2) EQATEC.Analytics.Monitor.Win32_vc100-x64.dll in Telerik Analytics Monitor Library before 3.2.125 allow local users to gain privileges via a Trojan horse (a) csunsapi.dll, (b) swift.dll, (c) nfhwcrhk.dll, or (d) surewarehook.dll file in an unspecified directory.
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 search order hijacking vulnerability in Telerik Analytics Monitor Library versions prior to 3.2.125. The affected DLLs (EQATEC.Analytics.Monitor.Win32_vc100.dll and its x64 counterpart) load additional DLLs from an untrusted search path, allowing local attackers to place malicious DLLs with specific names (csunsapi.dll, swift.dll, nfhwcrhk.dll, or surewarehook.dll) to achieve privilege escalation.
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<= 3.2.122CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:C/I:C/A:C
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 Telerik Analytics Monitor Library is installedSearch for EQATEC.Analytics.Monitor.Win32_vc100.dll or EQATEC.Analytics.Monitor.Win64_vc100.dll in the application directory, system directories, or PATH. Use commands like 'dir /s /b EQATEC.Analytics.Monitor.*.dll' or PowerShell 'Get-ChildItem -Recurse -Filter "EQATEC.Analytics.Monitor*.dll"'Affected if The vulnerable DLLs are found on the system
-
Determine the version of the installed Telerik Analytics Monitor LibraryRight-click the DLL and select Properties, then check the Version tab. Alternatively, use a tool like 'strings' to search for version metadata within the DLL, or check the installer/assembly manifest if available.Affected if The version is 3.2.122 or earlier (versions prior to 3.2.125 are vulnerable)
-
Verify the application runs from a secure directoryCheck the directory from which the application using Telerik Analytics Monitor Library is executed. Ensure it is not a world-writable directory (e.g., TEMP, public downloads, or network shares with broad access). Use 'icacls' or 'icacls <directory>' to inspect permissions.Affected if The application runs from a writable or shared directory accessible to other users
-
Inspect the application PATH for writable directoriesRun 'echo %PATH%' or 'Get-Item Env:PATH' to view the PATH variable. Check each directory for write permissions using 'icacls <directory>' or by attempting to create a test file. Attackers could place malicious DLLs in any writable directory that appears before the DLL location in PATH.Affected if The PATH contains writable directories that precede the location of the vulnerable DLLs
-
Check for suspicious DLLs in application directoriesSearch for the specific malicious DLL names mentioned in the advisory: csunsapi.dll, swift.dll, nfhwcrhk.dll, or surewarehook.dll. Use 'dir /s /b csunsapi.dll swift.dll nfhwcrhk.dll surewarehook.dll' in the application directory and PATH directories.Affected if Any of these specific DLL names are found in the application directory or PATH directories
A user is affected if Telerik Analytics Monitor Library version 3.2.122 or earlier is installed and the application runs from or has writable directories in its PATH that could allow an attacker to place malicious DLLs.
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 Telerik Analytics Monitor Library to version 3.2.125 or later. Alternatively, ensure the application runs from a secure directory and that the PATH does not include writable directories containing these specific DLL names.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2264 — 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-2264 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