# CVE-2022-1274: HTML Injection in Keycloak Admin REST API

> Attackers can inject arbitrary HTML into Keycloak emails, enabling phishing attacks against users of the identity management server.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Mar 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-m4fv-gm5m-4725

## What is CVE-2022-1274?

CVE-2022-1274 is a medium-severity cross-site scripting vulnerability in Redhat Keycloak, published on 29 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in Keycloak in the execute-actions-email endpoint. This issue allows arbitrary HTML to be injected into emails sent to Keycloak users and can be misused to perform phishing or other attacks against users.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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

2 open source packages ship an affected version, including org.keycloak:keycloak-services. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions | 20.0.5 |
| `org.keycloak:keycloak-services` | Maven | All versions | 20.0.5 |

Products: Redhat Keycloak, Redhat Openshift Container Platform, Redhat Single Sign-On.

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

Upgrade org.keycloak:keycloak-services to 20.0.5 or later.

## Is CVE-2022-1274 being exploited?

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

Public exploit code:

- https://github.com/shoucheng3/keycloak__keycloak_CVE-2022-1274_20-0-3 (github_poc): https://github.com/shoucheng3/keycloak__keycloak_CVE-2022-1274_20-0-3

## Other vulnerabilities in Redhat Keycloak

- [CVE-2022-4361](https://insights.sbomify.com/CVE-2022-4361/): Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC (critical 10.0)
- [CVE-2022-1245](https://insights.sbomify.com/CVE-2022-1245/): Keycloak vulnerable to privilege escalation on Token Exchange feature (critical 9.8)
- [CVE-2021-20195](https://insights.sbomify.com/CVE-2021-20195/): keycloak Self Stored Cross-site Scripting vulnerability (critical 9.6)
- [CVE-2019-14910](https://insights.sbomify.com/CVE-2019-14910/): Keycloak Authentication Error (critical 9.3)
- [CVE-2019-14909](https://insights.sbomify.com/CVE-2019-14909/): Keycloak Authentication Error (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1274 is a medium-severity cross-site scripting vulnerability in Redhat Keycloak, published on 29 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1274 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 20.0.5
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 20.0.5

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

## Sources

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

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