# CVE-2002-2163: Business logic in n/a

> Authenticated users can bypass voting restrictions by manipulating cookies, allowing multiple votes in the KvPoll application.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/A:N`)
- **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:** 16 Nov 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-gj5j-88f6-8jwm

## What is CVE-2002-2163?

CVE-2002-2163 is a medium-severity vulnerability in n/a, published on 16 Nov 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

KvPoll 1.1 allows remote authenticated users to vote more than once by setting the "already_voted" cookie by various methods, including a direct call to clear_cookies.php.

## Which versions are affected by CVE-2002-2163?

It affects 1 product.


Products: Killervault Kvpoll.

## How do I fix CVE-2002-2163?

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

## Is CVE-2002-2163 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2163 and fix it if it is affected.

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

## Sources

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

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