# CVE-2021-22661: Auth bypass in ICX35-HWC-A, ICX35-HWC-E

> Attackers can change the administrator password without knowing the current one, leading to unauthorized access on ICX35 controllers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 26 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cm5g-7gvh-66wv

## What is CVE-2021-22661?

CVE-2021-22661 is a high-severity authentication bypass vulnerability in ICX35-HWC-A, ICX35-HWC-E, published on 26 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Changing the password on the module webpage does not require the user to type in the current password first. Thus, the password could be changed by a user or external process without knowledge of the current password on the ICX35-HWC-A and ICX35-HWC-E (Versions 1.9.62 and prior).

Weakness: CWE-264

## Which versions are affected by CVE-2021-22661?

It affects 2 products.


Products: Prosoft-Technology Icx35-Hwc-a Firmware, Prosoft-Technology Icx35-Hwc-E Firmware.

## How do I fix CVE-2021-22661?

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

## Is CVE-2021-22661 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22661 and fix it if it is affected.

What it is: CVE-2021-22661 is a high-severity authentication bypass vulnerability in ICX35-HWC-A, ICX35-HWC-E, published on 26 Feb 2021. 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-2021-22661 in the wild and no public exploit code.

Affected product: ICX35-HWC-A, ICX35-HWC-E. 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-2021-22661/ (Markdown: https://insights.sbomify.com/CVE-2021-22661/index.md)
```

## Sources

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

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