Skip to content

avo vulnerable to stored cross-site scripting (XSS) in key_value field

High severity GitHub Reviewed Published Jan 16, 2024 in avo-hq/avo • Updated Jan 18, 2024

Package

bundler avo (RubyGems)

Affected versions

>= 3.0.0.beta1, <= 3.2.3
<= 2.46.0

Patched versions

3.2.4
2.47.0

Description

Summary

A stored cross-site scripting (XSS) vulnerability was found in the key_value field of Avo v3.2.3. This vulnerability could allow an attacker to execute arbitrary JavaScript code in the victim's browser.

Details

The value of the key_value is inserted directly into the HTML code. In the current version of Avo (possibly also older versions), the value is not properly sanitized before it is inserted into the HTML code.

This vulnerability can be exploited by an attacker to inject malicious JavaScript code into the key_value field. When a victim views the page containing the malicious code, the code will be executed in their browser.

In avo/fields/common/key_value_component.html.erb the value is taken in lines 38 and 49 and seems to be interpreted directly as html in lines 44 and 55.

PoC

POC

To reproduce the vulnerability, follow these steps:

  1. Edit an entry with a key_value field.
  2. Enter the following payload into the value field:
    POC\"> <script>alert( 'XSS in key_value' );</script> <strong>Outside-tag</strong
  3. Save the entry.
  4. Go to the index page and click on the eye icon next to the entry.

The malicious JavaScript code will be executed and an alert box will be displayed.
On the show and edit page the alert seems not to pop up, but the strong tag breaks out of the expected html tag

Impact

This vulnerability could be used to steal sensitive information from victims that could be used to hijack victims' accounts or redirect them to malicious websites.

References

@adrianthedev adrianthedev published to avo-hq/avo Jan 16, 2024
Published to the GitHub Advisory Database Jan 16, 2024
Reviewed Jan 16, 2024
Published by the National Vulnerability Database Jan 16, 2024
Last updated Jan 18, 2024

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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:L/UI:R/S:U/C:H/I:H/A:N

EPSS score

0.051%
(22nd percentile)

Weaknesses

CVE ID

CVE-2024-22191

GHSA ID

GHSA-ghjv-mh6x-7q6h

Source code

Credits

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