CVE-2008-4863
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 BPY_interface in Blender 2.46 allows local users to execute arbitrary code via a Trojan horse Python file in the current working directory, related to an erroneous setting of sys.path by the PySys_SetArgv function.
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 confidenceBPY_interface in Blender 2.46 incorrectly sets sys.path via PySys_SetArgv, causing the current working directory to be added to Python's module search path. This allows local attackers to place a malicious Python file (Trojan horse) in the directory where a user runs Blender, which will be automatically imported and executed when Blender loads its Python components.
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.46CVSS 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 installed Blender versionRun 'blender --version' or check the application bundle for version informationAffected if Version is exactly 2.46 (only this version is affected)
-
Determine the working directory used when launching BlenderNote the directory from which you typically execute the blender command or launch the applicationAffected if You run Blender from directories accessible to other users (shared folders, /tmp, download directories, or network mounts)
-
Check for unexpected Python files in your Blender run directoryList all .py files in the directory where you run Blender: 'ls -la *.py' in that directoryAffected if Any .py files exist that you did not create or expect, especially commonly imported names like 'os.py', 'sys.py', 'site.py', or 'blender.py'
-
Verify Python module import behaviorRun Blender with Python debugging: start Blender and inspect sys.path via 'python -c "import sys; print(sys.path)"' within Blender's Python environment, or check if importing fails when cwd contains a malicious moduleAffected if The current working directory appears in Python's sys.path (the first entry will be an empty string '' representing the current directory)
You are affected only if you have Blender version 2.46 AND run it from a directory where untrusted users could place malicious Python modules.
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 a patched version of Blender that corrects the sys.path handling. Avoid running Blender from untrusted or shared directories where attackers could place malicious Python modules.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-4863 — 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-2008-4863 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