ghsa-cjmm-x9x9-m2w5
Vulnerability from github
Summary
XSS can be triggered by review volumes
PoC
1. Access setting tab
2. Create new assets
3. In assets name inject payload: "<script>alert(1337)</script>
4. Click Utilities tab
5. Choose all volumes, or volume trigger xss
6. Click Update asset indexes.
7. Wait to assets update success.
8. Progress complete.
9. Click on review button will trigger XSS
Root cause
Function: index.php?p=admin/actions/asset-indexes/process-indexing-session&v=1680710595770 After loading completed, progess will load: "skippedEntries" and "missingEntries" These parameters is not yet filtered, I just tried "skippedEntries" but I think it will be work with "missingEntries"
My reponse:
{ "session": { "id": 10, "indexedVolumes": { "6": "\"" }, "totalEntries": 2235, "processedEntries": 2235, "cacheRemoteImages": true, "listEmptyFolders": false, "isCli": false, "actionRequired": true, "dateCreated": "Apr 5, 2023, 9:03:16 AM", "skippedEntries": [ "\"/assetpreviews/Image.php", "\"/assetpreviews/Pdf.php" ], "missingEntries": { "folders": [], "files": [] }, "processIfRootEmpty": false }, "skipDialog": false }
Resolved in https://github.com/craftcms/cms/commit/053d7119697e480ff81c5723bb9a33eaa49e0fc7
{ "affected": [ { "database_specific": { "last_known_affected_version_range": "\u003c= 4.4.6" }, "package": { "ecosystem": "Packagist", "name": "craftcms/cms" }, "ranges": [ { "events": [ { "introduced": "4.0.0-RC1" }, { "fixed": "4.4.7" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2023-33196" ], "database_specific": { "cwe_ids": [ "CWE-79", "CWE-80" ], "github_reviewed": true, "github_reviewed_at": "2023-05-26T13:55:42Z", "nvd_published_at": "2023-05-26T21:15:21Z", "severity": "MODERATE" }, "details": "### Summary\nXSS can be triggered by review volumes\n\n### PoC\n\n 1. Access setting tab\n 2. Create new assets\n 3. In assets name inject payload: \"\u003cscript\u003ealert(1337)\u003c/script\u003e\n 4. Click Utilities tab\n 5. Choose all volumes, or volume trigger xss\n 6. Click Update asset indexes.\n 7. Wait to assets update success.\n 8. Progress complete.\n 9. Click on review button will trigger XSS\n\n### Root cause\nFunction: index.php?p=admin/actions/asset-indexes/process-indexing-session\u0026v=1680710595770\nAfter loading completed, progess will load: \n\"skippedEntries\"\nand\n\"missingEntries\"\nThese parameters is not yet filtered, I just tried \"skippedEntries\" but I think it will be work with \"missingEntries\"\n\n### My reponse:\n{\n \"session\": {\n \"id\": 10,\n \"indexedVolumes\": {\n \"6\": \"\\\"\u003cscript\u003ealert(1337)\u003c/script\u003e\"\n },\n \"totalEntries\": 2235,\n \"processedEntries\": 2235,\n \"cacheRemoteImages\": true,\n \"listEmptyFolders\": false,\n \"isCli\": false,\n \"actionRequired\": true,\n \"dateCreated\": \"Apr 5, 2023, 9:03:16 AM\",\n \"skippedEntries\": [\n \"\\\"\u003cscript\u003ealert(1337)\u003c/script\u003e/assetpreviews/Image.php\",\n \"\\\"\u003cscript\u003ealert(1337)\u003c/script\u003e/assetpreviews/Pdf.php\"\n ],\n \"missingEntries\": {\n \"folders\": [],\n \"files\": []\n },\n \"processIfRootEmpty\": false\n },\n \"skipDialog\": false\n}\n\n\n\nResolved in https://github.com/craftcms/cms/commit/053d7119697e480ff81c5723bb9a33eaa49e0fc7", "id": "GHSA-cjmm-x9x9-m2w5", "modified": "2023-05-26T21:50:36Z", "published": "2023-05-26T13:55:42Z", "references": [ { "type": "WEB", "url": "https://github.com/craftcms/cms/security/advisories/GHSA-cjmm-x9x9-m2w5" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-33196" }, { "type": "WEB", "url": "https://github.com/craftcms/cms/commit/053d7119697e480ff81c5723bb9a33eaa49e0fc7" }, { "type": "PACKAGE", "url": "https://github.com/craftcms/cms" }, { "type": "WEB", "url": "https://github.com/craftcms/cms/releases/tag/4.4.7" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L", "type": "CVSS_V3" } ], "summary": "Craft CMS stored XSS in review volume" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.