CVE-2010-3164
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 Fenrir Sleipnir 2.9.4 and earlier and Grani 4.3 and earlier allows local users to gain privileges via a Trojan horse executable file in the current working 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 an untrusted search path (binary planting) vulnerability in Fenrir Sleipnir browser (version 2.9.4 and earlier) and Grani feed reader (version 4.3 and earlier). The applications execute a Trojan horse executable from the current working directory instead of using a fully qualified path, allowing local attackers to place a malicious executable with the same name in a directory where the vulnerable application runs, resulting in 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<= 2.9.4= 2.5.0= 2.5.1= 2.5.2= 2.5.3= 2.5.4= 2.5.5= 2.5.6= 2.5.7= 2.5.8= 2.5.9= 2.5.10<= 4.3= 3.0= 3.1= 3.2= 3.5= 4.0= 4.1= 4.2CVSS 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.
-
Check Fenrir Sleipnir versionOpen the application and go to Help > About, or locate the executable (typically in Program Files) and check file properties for version informationAffected if Version is 2.9.4 or earlier, or exactly matches 2.5.0 through 2.5.10
-
Check Grani versionOpen the application and go to Help > About, or locate the executable and check file properties for version informationAffected if Version is 4.3 or earlier, or exactly matches 3.0, 3.1, 3.2, 3.5, 4.0, 4.1, or 4.2
-
Identify typical execution locationNote the directory from which you typically launch Sleipnir or Grani. Check if it is a user-writable location such as a shared network folder, USB drive, or downloads folderAffected if The application is routinely launched from a directory where untrusted users can write files (shared folders, USB drives, download directories)
-
Scan for suspicious executablesSearch user-writable directories (especially where the application is run from) for executables with names matching common Windows system utilities such as cmd.exe, net.exe, reg.exe, or other program files that could be plantedAffected if Unexpected executables are found in directories where the vulnerable application runs, matching names of system utilities or the browser/reader executables themselves
You are affected if a vulnerable version of Fenrir Sleipnir or Grani is installed AND the application is run from or can be launched by users from directories writable by untrusted users, or suspicious executables exist in those directories.
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 patched versions of Fenrir Sleipnir and Grani. Additionally, ensure these applications are never run from directories writable by untrusted users (e.g., shared folders, USB drives) and remove any suspicious executables matching common program names from user-writable locations.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3164 — 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-2010-3164 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