# CVE-2008-7148: Code injection in n/a

> Attackers can execute arbitrary code by tricking users into opening a crafted .sif file in Synfig Animation Studio.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 1 Sep 2009
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2008-7148, GHSA-8g3v-qc9m-w846

## What is CVE-2008-7148?

CVE-2008-7148 is a critical code injection vulnerability in n/a, published on 1 Sep 2009. 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

Unspecified vulnerability in Synfig Animation Studio before 0.61.08 allows attackers to execute arbitrary code via a crafted .sif file.

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

It affects 1 product.


Products: Synfig Synfigstudio.

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

Upgrade to a fixed version.

## Is CVE-2008-7148 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7148 is a critical code injection vulnerability in n/a, published on 1 Sep 2009. 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-7148 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-7148/ (Markdown: https://insights.sbomify.com/CVE-2008-7148/index.md)
```

## Sources

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

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