Categories
CVE-2022-1274

Cross-Site Scripting (XSS) in org.keycloak:keycloak-services (CVE-2022-1274)

Summary

Cross-site scripting in org.keycloak:keycloak-services (CVE-2022-1274). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 20.0.5 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-1274 has been found in org.keycloak:keycloak-services.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.keycloak:keycloak-services to 20.0.5 or later.
If unsure, ask your IT team or search "org.keycloak:keycloak-services CVE-2022-1274" on the vendor's site.

CVE-2022-1274 (org.keycloak:keycloak-services) — CWE-79
Attack vector: remote (network-reachable)
Patched: 20.0.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in org.keycloak:keycloak-services.

📍 Affected scope

Check the vendor advisory for the affected versions of org.keycloak:keycloak-services.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 20.0.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.keycloak:keycloak-services を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.keycloak:keycloak-services to 20.0.5

    ステージング環境で 20.0.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven org.keycloak:keycloak-services
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.0.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details