# CVE-2022-26562: Auth bypass in n/a

> Attackers can bypass authentication checks for expired accounts in Kopano Core, allowing unauthorized access to the collaboration platform.

- **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:** Yes
- **Published:** 1 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-24g4-fh3x-4f5h, UBUNTU-CVE-2022-26562

## What is CVE-2022-26562?

CVE-2022-26562 is a critical authentication bypass vulnerability in n/a, published on 1 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in provider/libserver/ECKrbAuth.cpp of Kopano Core <= v11.0.2.51 contains an issue which allows attackers to authenticate even if the user account or password is expired. It also exists in the predecessor Zarafa Collaboration Platform (ZCP) in provider/libserver/ECPamAuth.cpp of Zarafa >= 6.30 (introduced between 6.30.0 RC1e and 6.30.8 final).

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Kopano Groupware Core.

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

Apply the vendor's patch.

## Is CVE-2022-26562 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19907](https://insights.sbomify.com/CVE-2019-19907/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-28994](https://insights.sbomify.com/CVE-2021-28994/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-26562 is a critical authentication bypass vulnerability in n/a, published on 1 Apr 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-26562 in the wild and no public exploit code.

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

## Sources

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

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