Skip to content

SmallRye Health UI Cross-site Scripting vulnerability

Moderate severity GitHub Reviewed Published Aug 26, 2022 to the GitHub Advisory Database • Updated Nov 16, 2023

Package

maven io.smallrye:smallrye-health-ui (Maven)

Affected versions

< 3.1.2

Patched versions

3.1.2

Description

It was found that the smallrye health metrics UI component did not properly sanitize some user inputs. An attacker could use this flaw to conduct cross-site scripting attacks.

References

Published by the National Vulnerability Database Aug 25, 2022
Published to the GitHub Advisory Database Aug 26, 2022
Reviewed Nov 16, 2023
Last updated Nov 16, 2023

Severity

Moderate

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
Changed
Confidentiality
Low
Integrity
Low
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:N/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.078%
(36th percentile)

Weaknesses

CVE ID

CVE-2021-3914

GHSA ID

GHSA-pvc3-wvxr-7cmf

Credits

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