# CVE-2007-4074: Command injection in n/a

> Attackers can execute arbitrary commands on Festival speech synthesis servers due to default configurations allowing unauthenticated access to the local daemon.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-4074, GHSA-jcxv-vj45-grr9

## What is CVE-2007-4074?

CVE-2007-4074 is a critical command injection vulnerability in Suse Suse Linux, published on 30 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of Centre for Speech Technology Research (CSTR) Festival 1.95 beta (aka 2.0 beta) on Gentoo Linux, SUSE Linux, and possibly other distributions, is run locally with elevated privileges without requiring authentication, which allows local and remote attackers to execute arbitrary commands via the local daemon on port 1314, a different vulnerability than CVE-2001-0956.  NOTE: this issue is local in some environments, but remote on others.

Weakness: CWE-16

## Which versions are affected by CVE-2007-4074?

It affects 2 products.


Products: Centre for Speech Technology Research Gentoo Linux, Suse Suse Linux.

## How do I fix CVE-2007-4074?

Change a configuration setting.

## Is CVE-2007-4074 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4074 and fix it if it is affected.

What it is: CVE-2007-4074 is a critical command injection vulnerability in Suse Suse Linux, published on 30 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4074 in the wild and no public exploit code.

Affected product: Suse Suse Linux. 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-2007-4074/ (Markdown: https://insights.sbomify.com/CVE-2007-4074/index.md)
```

## Sources

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

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