fix(extensions): manifest id is not validated and is used as a path with recursive delete (path traversal)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
Research direction
Read lib/core/extensions/models/extension_manifest.dart and the install paths in lib/core/extensions/local_extension_installer.dart; then inspect HttpMarketplaceRepository.install and uninstall for the corresponding path checks. Add the manifest ID validation and containment checks described in the issue, including the listed invalid IDs. Done means both installer paths reject traversal and the unit tests cover those IDs.
Written by the indexing model from the issue text.
Description
Problem
ExtensionManifest.fromJson reads the id as json['id'] as String with no validation (lib/core/extensions/models/extension_manifest.dart:114). The id is then used as a path segment:
LocalExtensionInstaller.installFromArchive:Directory(p.join(root.path, manifest.id)), and if it exists,extDir.delete(recursive: true)(lib/core/extensions/local_extension_installer.dart:123-128).HttpMarketplaceRepository.installanduninstall(extensionId):p.join(dir.path, manifest.id)/p.join(dir.path, extensionId),delete(recursive: true)in uninstall.
A sideloaded .qext with "id": "../../some/dir" makes the installer recursively delete a directory outside the extensions folder (and write the extracted files there). isArchiveEntryNameSafe only checks entry names inside the archive, not the manifest id.
Expected
- Validate the id in
ExtensionManifest.fromJson(e.g.^[A-Za-z0-9][A-Za-z0-9._-]*$, no separators, no..) and reject the manifest otherwise. - After
p.join, checkisArchiveExtractPathWithinRoot(root, extDir.path)before delete / create, in both installers and inuninstall. - Unit tests: ids
../x,a/b,..\x, absolute path, empty.
- Dominant language
- Dart
- Stars
- 23
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 496
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from QueryaHub/Querya-Desktop
-
bug P3 ux
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
QueryaHub/Querya-Desktop#1837 ·
Maintainers usually reply within 1 day
-
enhancement P3
Difficulty 4/5 3-5 days Newbie friendliness 50/100
QueryaHub/Querya-Desktop#1838 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
QueryaHub/Querya-Desktop#1690 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 1-2 days Newbie friendliness 55/100
QueryaHub/Querya-Desktop#1683 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
QueryaHub/Querya-Desktop#1625 · 2 comments ·
Maintainers usually reply within 1 day
All issues in QueryaHub/Querya-Desktop
Similar issues
-
area/ci-build bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
DarkFlippers/qUnleashed#423 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
google/skills_lint.dart#152 ·
Maintainers usually reply within 1 day
-
Docs: correct the unbuilt "full re-verify" claim and three untrue sync commentsPossibly taken @ibanner56 claimed this today. Openarea: sync priority: low severity: trivial type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ibanner56/CallersCompendium#1942 ·
Maintainers usually reply within 1 day
-
[Bug]: 编辑器替换栏关闭按钮错位Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
appshubcc/Bettbox#584 · 1 comment ·
Maintainers usually reply within 1 day