# CVE-2002-1747: Missing authorization in n/a

> Remote attackers can inject data into user sessions without authentication due to lack of packet verification in Vtun.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/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:** Yes
- **Published:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-1747, GHSA-hf68-wq7f-gmhq

## What is CVE-2002-1747?

CVE-2002-1747 is a medium-severity missing authorization vulnerability in n/a, published on 21 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vtun 2.5b1 does not authenticate forwarded packets, which allows remote attackers to inject data into user sessions without detection, and possibly control the data contents via cut-and-paste attacks on ECB.

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

It affects 1 product.


Products: Maxim Krasnyansky Vtun.

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

Upgrade to a fixed version.

## Is CVE-2002-1747 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1746](https://insights.sbomify.com/CVE-2002-1746/): Other in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1747 is a medium-severity missing authorization vulnerability in n/a, published on 21 Jun 2005. 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-2002-1747 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-1747/ (Markdown: https://insights.sbomify.com/CVE-2002-1747/index.md)
```

## Sources

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

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