# CVE-2022-27240: Memory corruption in n/a

> A buffer overflow in the webauthn assertion handling of Glewlwyd SSO server allows attackers to execute arbitrary code or cause a denial of service.

- **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:** 18 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-27240, UBUNTU-CVE-2022-27240

## What is CVE-2022-27240?

CVE-2022-27240 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

scheme/webauthn.c in Glewlwyd SSO server 2.x before 2.6.2 has a buffer overflow associated with a webauthn assertion.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Glewlwyd Sso Server Project Glewlwyd Sso Server.

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

Upgrade to a fixed version.

## Is CVE-2022-27240 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-49208](https://insights.sbomify.com/CVE-2023-49208/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-40818](https://insights.sbomify.com/CVE-2021-40818/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-25715](https://insights.sbomify.com/CVE-2024-25715/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27240 is a critical memory corruption vulnerability in n/a, published on 18 Mar 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-27240 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-27240/ (Markdown: https://insights.sbomify.com/CVE-2022-27240/index.md)
```

## Sources

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

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