# CVE-2010-5085: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to change passwords or site configuration via CSRF in Hulihan Amethyst.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Feb 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9g53-m8g7-vm8p

## What is CVE-2010-5085?

CVE-2010-5085 is a medium-severity vulnerability in n/a, published on 14 Feb 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in admin/update_user in Hulihan Amethyst 0.1.5, and possibly earlier, allow remote attackers to hijack the authentication of administrators for requests that (1) change the administrative password or (2) change the site's configuration.

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

## Which versions are affected by CVE-2010-5085?

It affects 1 product.


Products: Hulihanapplications Amethyst.

## How do I fix CVE-2010-5085?

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

## Is CVE-2010-5085 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-5085 and fix it if it is affected.

What it is: CVE-2010-5085 is a medium-severity vulnerability in n/a, published on 14 Feb 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2010-5085 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-2010-5085/ (Markdown: https://insights.sbomify.com/CVE-2010-5085/index.md)
```

## Sources

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

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