# CVE-2010-5067: Security feature bypass in n/a

> Remote attackers can bypass session timeouts and logout actions by leveraging static session cookies derived from passwords, retaining unauthorized access.

- **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:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-62cp-m7mw-jrpc

## What is CVE-2010-5067?

CVE-2010-5067 is a medium-severity vulnerability in n/a, published on 8 Oct 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Virtual War (aka VWar) 1.6.1 R2 uses static session cookies that depend only on a user's password, which makes it easier for remote attackers to bypass timeout and logout actions, and retain access for a long period of time, by leveraging knowledge of a session cookie.

Weakness: CWE-255

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

It affects 1 product.


Products: Vwar Virtual War.

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

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

## Is CVE-2010-5067 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-5063](https://insights.sbomify.com/CVE-2010-5063/): SQL injection in n/a (high 7.5)
- [CVE-2008-0753](https://insights.sbomify.com/CVE-2008-0753/): SQL injection in n/a (high 7.5)
- [CVE-2007-4605](https://insights.sbomify.com/CVE-2007-4605/): Code injection in n/a (high 7.5)
- [CVE-2007-2312](https://insights.sbomify.com/CVE-2007-2312/): SQL injection in n/a (high 7.5)
- [CVE-2006-4141](https://insights.sbomify.com/CVE-2006-4141/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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