# CVE-2008-6479: Cross-site request forgery in n/a

> Remote attackers can force authenticated users to change their passwords via CSRF, leading to account takeover in Parallels Virtuozzo.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gfh7-6m9h-pgf9

## What is CVE-2008-6479?

CVE-2008-6479 is a medium-severity vulnerability in n/a, published on 16 Mar 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in the "change password" feature in the VZPP web interface for Parallels Virtuozzo 25.4.swsoft (build 3.0.0-25.4.swsoft) allows remote attackers to modify the password via a link or IMG tag to vz/cp/pwd.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Parallels Parallels Virtuozzo.

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

No fix has been published for CVE-2008-6479 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-6479 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6479 exists.

Public exploit code:

- Parallels Virtuozzo Containers 3.0.0-25.4.swsoft VZPP Interface Change Pass - Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6479 is a medium-severity vulnerability in n/a, published on 16 Mar 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6479 exists.

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-6479/ (Markdown: https://insights.sbomify.com/CVE-2008-6479/index.md)
```

## Sources

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

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