# CVE-2024-23580: HCL DRYiCE Optibot Reset Station is impacted by insecure encryption of One-Time Passwords (OTPs)

> An attacker with database access can recover encrypted One-Time Passwords due to insecure encryption, compromising authentication security.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 28 May 2024
- **Updated:** 1 Aug 2024

## What is CVE-2024-23580?

CVE-2024-23580 is a medium-severity vulnerability in HCL Software DRYiCE Optibot Reset Station, published on 28 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HCL DRYiCE Optibot Reset Station is impacted by insecure encryption of One-Time Passwords (OTPs). This could allow an attacker with access to the database to recover some or all encrypted values.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2024-23580?


## How do I fix CVE-2024-23580?

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

## Is CVE-2024-23580 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23580 and fix it if it is affected.

What it is: CVE-2024-23580 is a medium-severity vulnerability in HCL Software DRYiCE Optibot Reset Station, published on 28 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23580 in the wild and no public exploit code.

Affected product: HCL Software DRYiCE Optibot Reset Station. 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-2024-23580/ (Markdown: https://insights.sbomify.com/CVE-2024-23580/index.md)
```

## Sources

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

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