Reflex arbitrary method call in stimulus_reflex
stimulusreflex stimulus_reflex
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| stimulus_reflex RubyGems |
|
|
| stimulus_reflex npm |
|
stimulusreflex stimulus_reflex
| Product | Affected | Fixed in |
|---|---|---|
| stimulus_reflex RubyGems |
|
|
| stimulus_reflex npm |
|
|
stimulus_reflex is a system to extend the capabilities of both Rails and Stimulus by intercepting user interactions and passing them to Rails over real-time websockets. In affected versions more methods than expected can be called on reflex instances. Being able to call some of them has security implications. To invoke a reflex a websocket message of the following shape is sent: `\"target\":\"[class_name]#[method_name]\",\"args\":[]`. The server will proceed to instantiate `reflex` using the provided `class_name` as long as it extends `StimulusReflex::Reflex`. It then attempts to call `method_name` on the instance with the provided arguments. This is problematic as `reflex.method method_name` can be more methods that those explicitly specified by the developer in their reflex class. A good example is the instance_variable_set method. This vulnerability has been patched in versions 3.4.2 and 3.5.0.rc4. Users unable to upgrade should: see the backing GHSA advisory for mitigation advice.
From the CVE record · GitHub_M
Affected stimulus_reflex versions allow more methods to be called on reflex instances than developers explicitly defined. An attacker who can send a reflex WebSocket message may invoke an unintended method; the input does not specify authentication requirements or user interaction.
Teams running the RubyGems or npm stimulus_reflex package should check versions below 3.4.2 and prerelease versions from 3.5.0.pre0 up to, but not including, 3.5.0.rc4 (npm: 3.5.0-pre0 to 3.5.0-rc4).