Unfettered User Authentication in Misconfigured Dusk Plugin
Summary
CVE-2024-32003: Dusk plugin may allow unfettered user authentication in misconfigured installs. Affects winter/wn-dusk-plugin versions < 2.1.0. Fixed in 2.1.0. How to fix ↓
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
Background
The Dusk plugin is a testing framework in Winter CMS that allows a browser environment to act as a user in the Backend or User plugin without authentication. It provides special routes for this purpose. However, if a Winter CMS installation using the Dusk plugin is misconfigured and publicly accessible, an attacker can potentially gain access to any user account without authentication. This vulnerability only affects Winter CMS instances with specific criteria.
Vulnerability Detail
The Dusk plugin in Winter CMS allows unfettered user authentication in misconfigured installations. By accessing a specific route, an attacker can bypass authentication and gain access to any user account in the Backend or User plugin. This vulnerability is low impact as it requires specific conditions to be met, including the Dusk plugin being installed, the application being in production mode, and the Dusk plugin's automatic configuration being overridden. The issue has been fixed in version 2.1.0 of the plugin.
How To Fix
Minimum fixed version
2.1.0
This is the first release that contains the fix.
composer require winter/wn-dusk-plugin:2.1.0Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround provided for this vulnerability. However, users can mitigate the risk by following the recommended steps to fix the issue.
Conclusion
The Dusk plugin in Winter CMS is vulnerable to unfettered user authentication in misconfigured installations. Winter CMS users should update the Dusk plugin to version 2.1.0 or later and follow the recommended steps to mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.
See every vulnerability recorded for winter/wn-dusk-plugin →
FAQ
The impact of this vulnerability is low as it requires specific conditions to be met. Only Winter CMS instances with the Dusk plugin installed, in production mode, and with overridden configuration are affected.
You can use the Vulert Playground at Vulert Scanner to check if your Winter CMS installation is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using composer.lock.
The CVSS score of this vulnerability is 8.8, indicating a high severity.
No, it is strongly recommended to only use the Dusk plugin in development and not in a production instance of Winter CMS.
You can update the Dusk plugin to version 2.1.0 or later by running the appropriate Composer command, such as 'composer require winter/wn-dusk-plugin:^2.1.0'.
