# CVE-2008-1103: Path traversal in n/a

> Attackers can exploit temporary file handling flaws in Blender to read or modify files, requiring user interaction to open a malicious file.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1103, GHSA-7hh3-qcf7-cr5r

## What is CVE-2008-1103?

CVE-2008-1103 is a medium-severity path traversal vulnerability in n/a, published on 28 Apr 2008. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Multiple unspecified vulnerabilities in Blender have unknown impact and attack vectors, related to "temporary file issues."

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2008-1103?

It affects 1 product.


Products: Blender Blender.

## How do I fix CVE-2008-1103?

Upgrade to a fixed version.

## Is CVE-2008-1103 being exploited?

There is no known exploitation of CVE-2008-1103 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2009-3850](https://insights.sbomify.com/CVE-2009-3850/): Code injection in n/a (critical 9.3)
- [CVE-2007-1253](https://insights.sbomify.com/CVE-2007-1253/): Code injection in n/a (critical 9.3)
- [CVE-2017-12081](https://insights.sbomify.com/CVE-2017-12081/): Integer overflow in Blender (high 8.8)
- [CVE-2017-12082](https://insights.sbomify.com/CVE-2017-12082/): Integer overflow in Blender (high 8.8)
- [CVE-2017-12086](https://insights.sbomify.com/CVE-2017-12086/): Integer overflow in Blender (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1103 and fix it if it is affected.

What it is: CVE-2008-1103 is a medium-severity path traversal vulnerability in n/a, published on 28 Apr 2008. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-1103 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-1103/ (Markdown: https://insights.sbomify.com/CVE-2008-1103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-1103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-1103
- OSV: https://osv.dev/vulnerability/CVE-2008-1103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-1103/
Summaries are generated and may contain mistakes; the official description above is the record.