# CVE-2022-22810: Auth bypass in spaceLYnk (V2.6.2 and prior), Wiser for KNX (formerly homeLYnk) (V2.6.2 and prior), fellerLYnk (V2.6.2 and prior)

> An attacker can gain admin access by brute-forcing credentials due to missing rate limiting on authentication attempts.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rwqj-v2jq-j266

## What is CVE-2022-22810?

CVE-2022-22810 is a critical authentication bypass vulnerability in spaceLYnk (V2.6.2 and prior), Wiser for KNX (formerly homeLYnk) (V2.6.2 and prior), fellerLYnk (V2.6.2 and prior), published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A CWE-307: Improper Restriction of Excessive Authentication Attempts vulnerability exists that could allow an attacker to manipulate the admin after numerous attempts at guessing credentials. Affected Product: spaceLYnk (V2.6.2 and prior), Wiser for KNX (formerly homeLYnk) (V2.6.2 and prior), fellerLYnk (V2.6.2 and prior)

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2022-22810?

It affects 3 products.


Products: Schneider-Electric Fellerlynk Firmware, Schneider-Electric Spacelynk Firmware, Schneider-Electric Wiser for Knx Firmware.

## How do I fix CVE-2022-22810?

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

## Is CVE-2022-22810 being exploited?

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

## Other vulnerabilities in spaceLYnk (V2.6.2 and prior), Wiser for KNX (formerly homeLYnk) (V2.6.2 and prior), fellerLYnk (V2.6.2 and prior)

- [CVE-2022-22811](https://insights.sbomify.com/CVE-2022-22811/): Cross-site request forgery in spaceLYnk (V2.6.2 and prior), Wiser for KNX (formerly homeLYnk) (V2.6.2 and prior), fellerLYnk (V2.6.2 and prior) (high 8.1)
- [CVE-2021-22806](https://insights.sbomify.com/CVE-2021-22806/): Information disclosure in spaceLYnk (V2.6.1 and prior), Wiser for KNX (V2.6.1 and prior), fellerLYnk (V2.6.1 and prior) (high 7.5)
- [CVE-2022-22812](https://insights.sbomify.com/CVE-2022-22812/): Cross-site scripting in spaceLYnk (V2.6.2 and prior), Wiser for KNX (formerly homeLYnk) (V2.6.2 and prior), fellerLYnk (V2.6.2 and prior) (medium 6.1)
- [CVE-2022-22809](https://insights.sbomify.com/CVE-2022-22809/): Missing authorization in spaceLYnk (V2.6.2 and prior), Wiser for KNX (formerly homeLYnk) (V2.6.2 and prior), fellerLYnk (V2.6.2 and prior) (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22810 and fix it if it is affected.

What it is: CVE-2022-22810 is a critical authentication bypass vulnerability in spaceLYnk (V2.6.2 and prior), Wiser for KNX (formerly homeLYnk) (V2.6.2 and prior), fellerLYnk (V2.6.2 and prior), published on 9 Feb 2022. 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-2022-22810 in the wild and no public exploit code.

Affected product: spaceLYnk (V2.6.2 and prior), Wiser for KNX (formerly homeLYnk) (V2.6.2 and prior), fellerLYnk (V2.6.2 and prior). 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-2022-22810/ (Markdown: https://insights.sbomify.com/CVE-2022-22810/index.md)
```

## Sources

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

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