Skip to content

Cross-Site Scripting Vulnerability in @joeattardi/emoji-button

High severity GitHub Reviewed Published Nov 26, 2021 in joeattardi/picmo • Updated Feb 1, 2023

Package

npm @joeattardi/emoji-button (npm)

Affected versions

< 4.6.2

Patched versions

4.6.2

Description

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.

References

@joeattardi joeattardi published to joeattardi/picmo Nov 26, 2021
Published by the National Vulnerability Database Nov 26, 2021
Reviewed Nov 29, 2021
Published to the GitHub Advisory Database Dec 1, 2021
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L

EPSS score

0.078%
(35th percentile)

Weaknesses

CVE ID

CVE-2021-43785

GHSA ID

GHSA-f34m-x9pj-62vq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.