# CVE-2006-6852: Code injection in n/a

> Authenticated users can execute arbitrary Ruby code in tDiary via eval injection in configuration files.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-6852, GHSA-2mq8-fvvr-mhhg

## What is CVE-2006-6852?

CVE-2006-6852 is a medium-severity code injection vulnerability in n/a, published on 4 Jan 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Eval injection vulnerability in tDiary 2.0.3 and 2.1.4.200 61127 allows remote authenticated users to execute arbitrary Ruby code via unspecified vectors, possibly related to incorrect input validation by (1) conf.rhtml and (2) i.conf.rhtml.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2006-6852?

It affects 1 product.


Products: Tdiary Tdiary.

## How do I fix CVE-2006-6852?

Upgrade to a fixed version.

## Is CVE-2006-6852 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2411](https://insights.sbomify.com/CVE-2005-2411/): Cross-site request forgery in n/a (medium 5.1)
- [CVE-2010-0726](https://insights.sbomify.com/CVE-2010-0726/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2006-6174](https://insights.sbomify.com/CVE-2006-6174/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6852 and fix it if it is affected.

What it is: CVE-2006-6852 is a medium-severity code injection vulnerability in n/a, published on 4 Jan 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6852 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-2006-6852/ (Markdown: https://insights.sbomify.com/CVE-2006-6852/index.md)
```

## Sources

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

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