Skip to content

Server-Side Request Forgery (SSRF) in Oxwall and Motoshub

Critical
mir-hossein published GHSA-7r26-qhvc-x695 Jul 14, 2022

Package

Motoshub

Affected versions

<= 11030

Patched versions

> 11030
Oxwall/Oxwall
<= 11111
> 11111

Description

Precisely similar to CVE-2021-36594 but it's another vulnerability:

SSRF in Oxwall <= 1.8.7 (11111), Motoshub <= 2 (11030) allows an attacker to execute arbitrary codes via internal API server or PHAR deserialization or ... via the "url" parameter.

Write-up (Root Cause Analysis + Technical details + Full Exploit Codes) will be published on my Blog later.
So please update!

Impact of this vulnerability on a target: (id)
SSRF2

Patches

According to the maintainers' claim, they patched this vulnerability for their premium users, but free users need to patch it manually (Please see Workarounds).

Workarounds

Please make these changes to your source code:
Oxwall:

Motoshub:

References

Motoshub
Motoshub/issues/1
Oxwall

For more information

If you have any questions or comments about this advisory:

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE ID

No known CVE

Weaknesses

Credits