# CVE-2002-1910: Weak cryptography in n/a

> Attackers can obtain user passwords due to the use of a reversible encryption algorithm in the Click2Learn Ingenium LMS.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 28 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xc56-2wgw-3623

## What is CVE-2002-1910?

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

### Official description

Click2Learn Ingenium Learning Management System 5.1 and 6.1 uses weak encryption for passwords (reversible algorithm), which allows attackers to obtain passwords.

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 1 product.


Products: Click-2 Ingenium Learning Management System.

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

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

## Is CVE-2002-1910 being exploited?

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

Public exploit code:

- Ingenium Learning Management System 5.1/6.1 - Reversible Password Hash (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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