MediumGHSA-cm46-gqf4-mv4fCVE-2024-51992

Orchid Platform has Method Exposure Vulnerability in Modals

Published 12 Nov 2024 · Updated 16 Dec 2024

Is your project on an affected orchid/platform?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=8.0 <14.43.0
Fixed in
14.43.0
Update to the fixed version for your release line, for example:composer require orchid/platform:^14.43.0

Details

Impact

This vulnerability is a method exposure issue (CWE-749: Exposed Dangerous Method or Function) in the Orchid Platform’s asynchronous modal functionality, affecting users of Orchid Platform version 8 through 14.42.x. Attackers could exploit this vulnerability to call arbitrary methods within the Screen class, leading to potential brute force of database tables, validation checks against user credentials, and disclosure of the server’s real IP address.

Patches

The issue has been patched in the latest release, version 14.43.0, released on November 6, 2024. Users should upgrade to version 14.43.0 or later to address this vulnerability.

Workarounds

If upgrading to version 14.43.0 is not immediately possible, you can mitigate the vulnerability by implementing middleware to intercept and validate requests to asynchronous modal endpoints, allowing only approved methods and parameters.

Example middleware:

namespace App\Http\Middleware;

use Closure;
use Illuminate\Http\Request;
use Symfony\Component\HttpFoundation\Response;

class PreventBruteForceOnAsyncRoute
{
    /**
     * Methods that are restricted from being invoked via the async route.
     */
    protected array $restrictedMethods = [
        'validate',
        'handle',
        '__invoke',
        'validateWith',
        'validateWithBag',
        'callAction',
    ];

    /**
     * Handle an incoming request.
     */
    public function handle(Request $request, Closure $next): Response
    {
        // Retrieve the current route from the request.
        /** @var \Illuminate\Routing\Route|null $route */
        $route = $request->route();

        // Allow requests to routes other than "platform.async".
        if ($route?->getName() !== 'platform.async') {
            return $next($request);
        }

        // Block requests attempting to invoke any of the restricted methods.
        if (in_array($route->parameter('method'), $this->restrictedMethods)) {
            abort(503, sprintf(
                'Access to the "%s" method is restricted.',
                $route->parameter('method')
            ));
        }

        // Continue request processing for other cases.
        return $next($request);
    }
}

References

Acknowledgements

We would like to extend our sincere gratitude to Positive Technologies and researcher Vladislav Gladky for identifying the vulnerability and their significant contribution to enhancing the security of our platform. Their expertise and dedication play a crucial role in making Orchid more reliable and secure for all users.

Is GHSA-cm46-gqf4-mv4f in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected orchid/platform, and gives you the command that fixes it.

More advisories for orchid/platform

  • CriticalCVE-2023-36825Orchid Deserialization of Untrusted Data vulnerability leads to Remote Code Execution · 11 Jul 2023
  • HighCVE-2020-15263Inline attribute values were not processed. · 19 Oct 2020
orchid/platform security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.