# CVE-2011-0910: Weak cryptography in n/a

> Remote attackers can spoof signed requests via HMAC timing attacks to gain unauthorized access to arbitrary user accounts in Vanilla Forums.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rhp4-wj2m-wjjx

## What is CVE-2011-0910?

CVE-2011-0910 is a medium-severity vulnerability in n/a, published on 8 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The cookie implementation in Vanilla Forums before 2.0.17.6 makes it easier for remote attackers to spoof signed requests, and consequently obtain access to arbitrary user accounts, via HMAC timing attacks.

## Which versions are affected by CVE-2011-0910?

It affects 1 product.


Products: Vanillaforums Vanilla.

## How do I fix CVE-2011-0910?

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

## Is CVE-2011-0910 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3614](https://insights.sbomify.com/CVE-2011-3614/): Missing authorization in Vanilla Forums (critical 9.8)
- [CVE-2018-18903](https://insights.sbomify.com/CVE-2018-18903/): Code injection in n/a (critical 9.8)
- [CVE-2011-3613](https://insights.sbomify.com/CVE-2011-3613/): Information disclosure in Vanilla Forums (high 7.5)
- [CVE-2016-10073](https://insights.sbomify.com/CVE-2016-10073/): Information disclosure in n/a (high 7.5)
- [CVE-2013-3527](https://insights.sbomify.com/CVE-2013-3527/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0910 and fix it if it is affected.

What it is: CVE-2011-0910 is a medium-severity vulnerability in n/a, published on 8 Feb 2011. 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-2011-0910 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-2011-0910/ (Markdown: https://insights.sbomify.com/CVE-2011-0910/index.md)
```

## Sources

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

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