# CVE-2002-0197: Security feature bypass in n/a

> Remote attackers can spoof trusted encrypted messages in psyBNC by using specific line prefixes, bypassing security controls.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hqv3-5f62-wr2j

## What is CVE-2002-0197?

CVE-2002-0197 is a high-severity vulnerability in n/a, published on 25 Jun 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

psyBNC 2.3 beta and earlier allows remote attackers to spoof encrypted, trusted messages by sending lines that begin with the "[B]" sequence, which makes the message appear legitimate.

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

It affects 1 product.


Products: Psychoid Psybnc.

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

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

## Is CVE-2002-0197 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0741](https://insights.sbomify.com/CVE-2002-0741/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0197 is a high-severity vulnerability in n/a, published on 25 Jun 2002. 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-0197 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-0197/ (Markdown: https://insights.sbomify.com/CVE-2002-0197/index.md)
```

## Sources

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

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