Advisory details:
github_osv / GHSA-xgr2-v94m-rc9g
| Advisory ID | github_osv/GHSA-xgr2-v94m-rc9g |
| Aliases |
CVE-2013-0333
|
| Summary | activesupport in Rails vulnerable to incorrect data conversion `lib/active_support/json/backends/yaml.rb` in Ruby on Rails 2.3.x before 2.3.16 and 3.0.x before 3.0.20 does not properly convert JSON data to YAML data for processing by a YAML parser, which allows remote attackers to execute arbitrary code, conduct SQL injection attacks, or bypass authentication via crafted data that triggers unsafe decoding, a different vulnerability than CVE-2013-0156. |
| Status | Published |
| Exploitability | 2.0 |
| Weighted Severity | 0.0 |
| Risk | |
| Affected and Fixed Packages | Package Details |
| Introduced and Fixed Package Commit Patches | Package Commit Patches Details |
| There are no known CWE. |
| System | Score | Found at |
|---|---|---|
| generic_textual | HIGH |
| Data source | Metasploit |
|---|---|
| Description | This module exploits a remote code execution vulnerability in the JSON request processor of the Ruby on Rails application framework. This vulnerability allows an attacker to instantiate a remote object, which in turn can be used to execute any ruby code remotely in the context of the application. This vulnerability is very similar to CVE-2013-0156. This module has been tested successfully on RoR 3.0.9, 3.0.19, and 2.3.15. The technique used by this module requires the target to be running a fairly recent version of Ruby 1.9 (since 2011 or so). Applications using Ruby 1.8 may still be exploitable using the init_with() method, but this has not been demonstrated. |
| Note | Reliability: - unknown-reliability Stability: - unknown-stability SideEffects: - unknown-side-effects |
| Ransomware campaign use | Unknown |
| Source publication date | Jan. 28, 2013 |
| Platform | Ruby |
| Source URL | https://github.com/rapid7/metasploit-framework/tree/master/modules/exploits/multi/http/rails_json_yaml_code_exec.rb |
| Data source | Exploit-DB |
|---|---|
| Date added | Jan. 29, 2013 |
| Description | Ruby on Rails - JSON Processor YAML Deserialization Code Execution (Metasploit) |
| Ransomware campaign use | Known |
| Source publication date | Jan. 29, 2013 |
| Exploit type | remote |
| Platform | multiple |
| Source update date | Jan. 29, 2013 |
| Data source | Metasploit |
|---|---|
| Description | This module attempts to identify Ruby on Rails instances vulnerable to an arbitrary object instantiation flaw in the JSON request processor. |
| Note | Reliability: - unknown-reliability Stability: - unknown-stability SideEffects: - unknown-side-effects |
| Ransomware campaign use | Unknown |
| Source URL | https://github.com/rapid7/metasploit-framework/tree/master/modules/auxiliary/scanner/http/rails_json_yaml_scanner.rb |
| Data source | Metasploit |
|---|---|
| Description | This module exploits a remote code execution vulnerability in the JSON request processor of the Ruby on Rails application framework. This vulnerability allows an attacker to instantiate a remote object, which in turn can be used to execute any ruby code remotely in the context of the application. This vulnerability is very similar to CVE-2013-0156. This module has been tested successfully on RoR 3.0.9, 3.0.19, and 2.3.15. The technique used by this module requires the target to be running a fairly recent version of Ruby 1.9 (since 2011 or so). Applications using Ruby 1.8 may still be exploitable using the init_with() method, but this has not been demonstrated. |
| Note | Reliability: - unknown-reliability Stability: - unknown-stability SideEffects: - unknown-side-effects |
| Ransomware campaign use | Unknown |
| Source publication date | Jan. 28, 2013 |
| Platform | Ruby |
| Source URL | https://github.com/rapid7/metasploit-framework/tree/master/modules/exploits/multi/http/rails_json_yaml_code_exec.rb |
| Data source | Exploit-DB |
|---|---|
| Date added | Jan. 29, 2013 |
| Description | Ruby on Rails - JSON Processor YAML Deserialization Code Execution (Metasploit) |
| Ransomware campaign use | Known |
| Source publication date | Jan. 29, 2013 |
| Exploit type | remote |
| Platform | multiple |
| Source update date | Jan. 29, 2013 |
No EPSS data available for this advisory.
| Patch URL | |
|---|---|
| There are no known patches. | |
There are no known vectors.
There are no SSVC decisions available.