# CVE-2000-1173: Weak cryptography in n/a

> Attackers can sniff network traffic to obtain sensitive registration data and credit card numbers due to weak or missing encryption.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 19 Dec 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7rc9-qwrm-pj39

## What is CVE-2000-1173?

CVE-2000-1173 is a medium-severity vulnerability in n/a, published on 19 Dec 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsys CyberPatrol uses weak encryption (trivial encoding) for credit card numbers and uses no encryption for the remainder of the information during registration, which could allow attackers to sniff network traffic and obtain this sensitive information.

## Which versions are affected by CVE-2000-1173?

It affects 1 product.


Products: Microsys Cyberpatrol.

## How do I fix CVE-2000-1173?

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

## Is CVE-2000-1173 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-1173 exists.

Public exploit code:

- Microsys CyberPatrol 4.0 4.003/4.0 4.005 - Insecure Registration (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-1173 and fix it if it is affected.

What it is: CVE-2000-1173 is a medium-severity vulnerability in n/a, published on 19 Dec 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-1173 exists.

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-2000-1173/ (Markdown: https://insights.sbomify.com/CVE-2000-1173/index.md)
```

## Sources

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

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