GHSA-CM46-GQF4-MV4F
Vulnerability from github – Published: 2024-11-12 19:56 – Updated: 2024-12-16 15:27Impact
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.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "orchid/platform"
},
"ranges": [
{
"events": [
{
"introduced": "8.0"
},
{
"fixed": "14.43.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-51992"
],
"database_specific": {
"cwe_ids": [
"CWE-749"
],
"github_reviewed": true,
"github_reviewed_at": "2024-11-12T19:56:54Z",
"nvd_published_at": "2024-11-11T20:15:19Z",
"severity": "MODERATE"
},
"details": "### Impact\nThis vulnerability is a method exposure issue (CWE-749: Exposed Dangerous Method or Function) in the Orchid Platform\u2019s 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\u2019s real IP address.\n\n### Patches\nThe 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.\n\n### Workarounds\nIf 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.\n\n\nExample middleware:\n\n```php\nnamespace App\\Http\\Middleware;\n\nuse Closure;\nuse Illuminate\\Http\\Request;\nuse Symfony\\Component\\HttpFoundation\\Response;\n\nclass PreventBruteForceOnAsyncRoute\n{\n /**\n * Methods that are restricted from being invoked via the async route.\n */\n protected array $restrictedMethods = [\n \u0027validate\u0027,\n \u0027handle\u0027,\n \u0027__invoke\u0027,\n \u0027validateWith\u0027,\n \u0027validateWithBag\u0027,\n \u0027callAction\u0027,\n ];\n\n /**\n * Handle an incoming request.\n */\n public function handle(Request $request, Closure $next): Response\n {\n // Retrieve the current route from the request.\n /** @var \\Illuminate\\Routing\\Route|null $route */\n $route = $request-\u003eroute();\n\n // Allow requests to routes other than \"platform.async\".\n if ($route?-\u003egetName() !== \u0027platform.async\u0027) {\n return $next($request);\n }\n\n // Block requests attempting to invoke any of the restricted methods.\n if (in_array($route-\u003eparameter(\u0027method\u0027), $this-\u003erestrictedMethods)) {\n abort(503, sprintf(\n \u0027Access to the \"%s\" method is restricted.\u0027,\n $route-\u003eparameter(\u0027method\u0027)\n ));\n }\n\n // Continue request processing for other cases.\n return $next($request);\n }\n}\n```\n\n### References\n- [CWE-749: Exposed Dangerous Method or Function](https://cwe.mitre.org/data/definitions/749.html)\n\n### Acknowledgements\n\nWe 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.\n",
"id": "GHSA-cm46-gqf4-mv4f",
"modified": "2024-12-16T15:27:59Z",
"published": "2024-11-12T19:56:54Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/orchidsoftware/platform/security/advisories/GHSA-cm46-gqf4-mv4f"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-51992"
},
{
"type": "PACKAGE",
"url": "https://github.com/orchidsoftware/platform"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Orchid Platform has Method Exposure Vulnerability in Modals"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.