{"id":16683,"date":"2021-07-07T16:26:17","date_gmt":"2021-07-07T14:26:17","guid":{"rendered":"https:\/\/herolab-usd.formwandler.rocks\/security-advisories\/usd-2020-0031\/"},"modified":"2021-07-19T14:15:40","modified_gmt":"2021-07-19T12:15:40","slug":"usd-2020-0031","status":"publish","type":"page","link":"https:\/\/herolab.usd.de\/en\/security-advisories\/usd-2020-0031\/","title":{"rendered":"usd-2020-0031"},"content":{"rendered":"

[et_pb_section fb_built=\"1\" _builder_version=\"4.9.4\" _module_preset=\"default\" background_color=\"#2E353D\" custom_padding=\"||0px|||\"][et_pb_row _builder_version=\"4.9.4\" _module_preset=\"default\"][et_pb_column type=\"4_4\" _builder_version=\"4.9.4\" _module_preset=\"default\"][et_pb_text _builder_version=\"4.9.4\" _module_preset=\"cc5ac6f4-ebbd-4b3f-bc92-4dfc1f15fe2c\"]<\/p>\n

usd-2020-0031 | Gambio GX 4.0.0.0<\/span><\/h1>\n

<\/span>
Advisory ID<\/strong>: usd-2020-0031<\/span>
CVE Number<\/strong>: CVE-2020-10984<\/span>
Affected Product<\/strong>: Gambio GX<\/span>
Affected Version<\/strong>: 4.0.0.0<\/span>
Vulnerability Type<\/strong>: Cross-Site-Request-Forgery (CSRF)<\/span>
Security Risk<\/strong>: Critical<\/span>
Vendor URL<\/strong>: https:\/\/www.gambio.de\/<\/a><\/span>
Vendor Status<\/strong>: Fixed in 4.0.1.0 (according to vendor)<\/span><\/p>\n

<\/h3>\n

Description<\/h3>\n

The open source application is vulnerable to a number of Cross-Site Request Forgery (CSRF) attacks. CSRF is an attack that forces an end user to execute unwanted actions on a web application in which they are currently authenticated. A lot of critical functions are executed from the shop backend which is not secured against CSRF attacks. In the worst case CSRF can lead to code execution.<\/span><\/p>\n

<\/span><\/p>\n

Proof of Concept (PoC)<\/h3>\n

An attacker could create an HTML page with the following content:<\/span><\/p>\n

[\/et_pb_text][et_pb_image src=\"https:\/\/herolab.usd.de\/wp-content\/uploads\/sites\/9\/2021\/07\/usd20200031-1.png\" title_text=\"usd20200031-1\" _builder_version=\"4.9.4\" _module_preset=\"default\" custom_margin=\"27px||43px||false|false\"][\/et_pb_image][et_pb_text _builder_version=\"4.9.4\" _module_preset=\"default\"]<\/p>\n

An already authenticated backend user who visits the attacker\u2019s site and presses the \u201eSubmit request\u201c button would, unknowingly, upload a php file. The file will be stored into \/media\/content\/webshell.php<\/em>\u00a0and allow code execution for the attacker.<\/p>\n

The following request allows an attacker to view the \/etc\/passwd<\/em>\u00a0file:<\/p>\n

[\/et_pb_text][et_pb_image src=\"https:\/\/herolab.usd.de\/wp-content\/uploads\/sites\/9\/2021\/07\/usd20200031-2.png\" title_text=\"usd20200031-2\" _builder_version=\"4.9.4\" _module_preset=\"default\"][\/et_pb_image][et_pb_text _builder_version=\"4.9.4\" _module_preset=\"cc5ac6f4-ebbd-4b3f-bc92-4dfc1f15fe2c\"]<\/p>\n

\n
\n

Fix<\/h3>\n

By using token-based requests CSRF can be prevented. It can be achieved either with state (synchronizer token pattern) or stateless (encrypted or hashed based token pattern). CSRF tokens should be generated on the server-side. They can either be generated once per user session or for each request. An attacker would therefore have to guess or know the randomly generated token for a successful attack.<\/span><\/p>\n

<\/h3>\n

Timeline<\/h3>\n