CVE-2010-3163
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 before 2.9.5 and Grani before 4.4 allows local users to gain privileges via a Trojan horse DLL 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 a DLL hijacking (untrusted search path) vulnerability in Fenrir Sleipnir and Grani browsers. The applications load dynamic-link libraries from the current working directory without validating the DLL path, allowing a local attacker to place a malicious DLL that gets loaded with the application's privileges, enabling 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 if Fenrir Sleipnir is installedLook for Sleipnir executable (Sleipnir.exe) in common installation paths such as C:\Program Files\Fenrir\Sleipnir\ or C:\Program Files\Sleipnir\Affected if The executable is found on the system
-
Determine installed version of Fenrir SleipnirRight-click Sleipnir.exe, select Properties, and check the Version tab for the product versionAffected if The version is 2.5.0 through 2.5.10, or 2.9.4 or lower
-
Check if Fenrir Grani is installedLook for Grani executable (Grani.exe) in common installation paths such as C:\Program Files\Fenrir\Grani\ or C:\Program Files\Grani\Affected if The executable is found on the system
-
Determine installed version of Fenrir GraniRight-click Grani.exe, select Properties, and check the Version tab for the product versionAffected if The version is 3.0, 3.1, 3.2, 3.5, 4.0, 4.1, 4.2, or 4.3 or lower
-
Verify launch directory permissionsIdentify the directory from which the browser is typically launched; check if untrusted users have write permissions to that directory using file system permissionsAffected if The application is launched from a directory writable by untrusted users (such as downloads folder, desktop, or network share)
A user is affected if either Fenrir Sleipnir version 2.5.0-2.5.10 or <=2.9.4, or Fenrir Grani version 3.0-4.3 or <=4.3, is installed AND the application is launched from a directory writable by untrusted users.
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 Fenrir Sleipnir 2.9.5 or Grani 4.4 or later, which contain the fix. As a workaround, ensure these applications are never launched from directories writable by untrusted users.
- 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-2010-3163 — 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-3163 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