Variable Tampering within joomla/input class
Summary
CVE-2022-23799: Variable Tampering within joomla/input class. Affects joomla/input versions >= 2.0.0, < 2.0.2. Fixed in 2.0.2. How to fix ↓
Also tracked for
- joomla · Bitnami
The same CVE-2022-23799 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The joomla/input package is a component of the Joomla! CMS framework. It provides functionality for handling user input, including sanitization and validation. This package is widely used in Joomla! applications to process user data and ensure its security. However, a vulnerability has been discovered in versions 4.0.0 through 4.1.0 of Joomla!, specifically within the joomla/input class. This vulnerability allows for variable tampering under specific circumstances, resulting in the pollution of method-specific input bags with $_REQUEST data.
Vulnerability Detail
The vulnerability arises due to a flaw in the JInput class of the joomla/input package. When certain conditions are met, the class does not properly separate input data, leading to the mixing of method-specific input bags with the global $_REQUEST data. This can result in the manipulation of variables and potentially allow an attacker to perform unauthorized actions or access sensitive information. The impact of this vulnerability is considered critical, with a CVSS score of 9.8. It is crucial to address this issue promptly to prevent potential exploitation.
How To Fix
Minimum fixed version
2.0.2
This is the first release that contains the fix.
composer require joomla/input:2.0.2Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, developers can manually sanitize and validate user input before processing it with the joomla/input package. This can involve implementing custom input handling logic or utilizing alternative input filtering libraries. However, applying the official fix by updating the package is the recommended approach.
Conclusion
In conclusion, the joomla/input package in Joomla! versions 4.0.0 through 4.1.0 is vulnerable to variable tampering, which can lead to unauthorized actions or access to sensitive information. It is crucial to update the package to version 2.0.2 or later to mitigate this issue. Developers can also utilize the Vulert Playground at https://vulert.com/scanner to check if their application is affected by this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for joomla/input →
FAQ
The vulnerability allows for variable tampering, which can lead to unauthorized actions or access to sensitive information within Joomla! applications.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your composer.lock file, and Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this advisory, there is no known public exploit for this vulnerability. However, it is crucial to address it promptly to prevent potential exploitation.
No, only versions 4.0.0 through 4.1.0 of Joomla! are affected by this vulnerability. It is recommended to update to the latest version of the joomla/input package to mitigate the issue.
The CVSS score of this vulnerability is 9.8, indicating its critical severity.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
