Cross-Site Scripting (XSS) in com.adobe.acs:acs-aem-commons (CVE-2022-28820)
Summary
Cross-site scripting in com.adobe.acs:acs-aem-commons (CVE-2022-28820). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.2.0 or later.
Original description
The description as published by the source.
ACS Commons version 5.1.x (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in /apps/acs-commons/content/page-compare.html endpoint via the a and b GET parameters. User input submitted via these parameters is not validated or sanitised. An attacker must provide a link to someone with access to AEM Author, and could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim's browser. The exploitation of this issue requires user interaction in order to be successful.
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-28820 has been found in com.adobe.acs:acs-aem-commons.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.adobe.acs:acs-aem-commons to 5.2.0 or later.
If unsure, ask your IT team or search "com.adobe.acs:acs-aem-commons CVE-2022-28820" on the vendor's site.
CVE-2022-28820 (com.adobe.acs:acs-aem-commons) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Patched: 5.2.0 — 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.
Cross-site scripting (XSS) (CWE-79) exists in com.adobe.acs:acs-aem-commons.
Check the vendor advisory for the affected versions of com.adobe.acs:acs-aem-commons.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.2.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.adobe.acs:acs-aem-commons を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.adobe.acs:acs-aem-commons to 5.2.0ステージング環境で 5.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com