Cross-Site Scripting (XSS) in @joeattardi/emoji-button (CVE-2021-43785)
Summary
Cross-site scripting in @joeattardi/emoji-button (CVE-2021-43785). Confidential information can be exposed externally. Exploitable via script. Mitigation: upgrade to 4.6.2 or later.
Original description
The description as published by the source.
Impact
There are two vectors for XSS attacks with versions of @joeattardi/emoji-button before 4.6.2:
- A URL for a custom emoji
- An i18n string
In both of these cases, a value can be crafted such that it can insert a script tag into the page and execute malicious code.
Patches
This vulnerability is fixed starting in version 4.6.2. This is resolved by properly escaping strings that are inserted into the HTML document.
Workarounds
There is no workaround other than upgrading to a non-vulnerable version.
Credit
This issue was discovered by GitHub team member @erik-krogh (Erik Krogh Kristensen) and was reported by the GitHub Security Lab team.
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-2021-43785 has been found in @joeattardi/emoji-button.
Attackers can target a specific entry point like script over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade @joeattardi/emoji-button to 4.6.2 or later.
If unsure, ask your IT team or search "@joeattardi/emoji-button CVE-2021-43785" on the vendor's site.
CVE-2021-43785 (@joeattardi/emoji-button) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: script
Patched: 4.6.2 — apply immediately
Workaround: There is no workaround other than upgrading to a non-vulnerable version.
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 @joeattardi/emoji-button. Attackers reach the vulnerable code path via script without authentication.
Check the vendor advisory for the affected versions of @joeattardi/emoji-button. Attack surface: script.
Severity: ?. Confidential information can be exposed externally.
Update to 4.6.2.
Workaround: There is no workaround other than upgrading to a non-vulnerable version.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@joeattardi/emoji-button' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@joeattardi/emoji-button' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@joeattardi/emoji-buttonを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There is no workaround other than upgrading to a non-vulnerable version.パッチが適用されるまでの応急処置として、There is no workaround other than upgrading to a non-vulnerable version. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @joeattardi/emoji-button to 4.6.2ステージング環境で 4.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com