CVE-2022-4520: WSO2 carbon-registry Cross-site Scripting vulnerability

Summary

15/12/2022
Yes i
Moderate
6.1

CVE-2022-4520: WSO2 carbon-registry Cross-site Scripting vulnerability. Affects org.wso2.carbon.registry:carbon-registry versions < 4.8.12. Fixed in 4.8.12. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

WSO2 carbon-registry is an open-source registry for managing and storing various types of assets. It provides functionality for advanced search operations. However, versions up to 4.8.11 are vulnerable to a cross-site scripting (XSS) attack. This vulnerability can be exploited remotely and affects the 'Advanced Search' component of the registry.

Vulnerability Detail

The vulnerability exists in the 'advancedSearchForm-ajaxprocessor.jsp' file located in the 'components/registry/org.wso2.carbon.registry.search.ui/src/main/resources/web/search' directory. By manipulating the 'mediaType/rightOp/leftOp/rightPropertyValue/leftPropertyValue' argument, an attacker can inject malicious scripts into the application, leading to cross-site scripting. This can potentially allow the attacker to steal sensitive information or perform unauthorized actions on behalf of the user. The severity of this vulnerability is rated as MODERATE with a CVSS score of 6.1.

How To Fix

Minimum fixed version

4.8.12

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

The WSO2 carbon-registry up to version 4.8.11 is vulnerable to a cross-site scripting (XSS) attack. To mitigate this vulnerability, it is advised to upgrade to version 4.8.12 or apply the provided patch. Proper input validation and output encoding should also be implemented to prevent XSS attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.wso2.carbon.registry:carbon-registry →

Share this vulnerability

FAQ

The vulnerability allows an attacker to execute arbitrary scripts on the affected application, potentially leading to unauthorized access, data theft, or other malicious activities.

Yes, the vulnerability can be exploited remotely by sending specially crafted requests to the affected application.

Yes, upgrading to version 4.8.12 of WSO2 carbon-registry or applying the provided patch can fix this vulnerability.

The recommended mitigation is to upgrade to the fixed version or apply the provided patch. Additionally, implementing proper input validation and output encoding can help prevent XSS attacks.

There is no specific evidence mentioned regarding active exploitation of this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for org.wso2.carbon.registry:carbon-registry.

How To Fix

Minimum fixed version

4.8.12

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback