Skip to content

WSO2 carbon-registry vulnerable to Cross-site Scripting

Moderate severity GitHub Reviewed Published Dec 15, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

maven org.wso2.carbon.registry:carbon-registry (Maven)

Affected versions

< 4.8.7

Patched versions

4.8.7

Description

A vulnerability classified as problematic has been found in WSO2 carbon-registry before 4.8.7. This affects an unknown part of the component Request Parameter Handler. The manipulation of the argument parentPath/path/username/path/profile_menu leads to cross site scripting. It is possible to initiate the attack remotely. Upgrading to version 4.8.7 or later will address this issue. The name of the patch is 9f967abfde9317bee2cda469dbc09b57d539f2cc. It is recommended to upgrade the affected component. The identifier VDB-215901 was assigned to this vulnerability.

References

Published by the National Vulnerability Database Dec 15, 2022
Published to the GitHub Advisory Database Dec 15, 2022
Reviewed Dec 15, 2022
Last updated Jan 27, 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.086%
(38th percentile)

Weaknesses

CVE ID

CVE-2022-4521

GHSA ID

GHSA-gp5f-gqgq-7254

Source code

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