User tests: Successful: Unsuccessful:
Pull Request for Issue # .
This pull request (PR) fixes one high severity and one moderate severity security vulnerability in indirect NPM development dependencies reported by npm audit by using npm audit fix.
Same as PR #46502 for 5.4-dev, but here for 6.0-dev to avoid ugly merge conflicts for the upmerge after that.
It needs a development environment with a git clone, composer and npm.
composer install and npm ci.npm audit.# npm audit report
glob 11.0.0 - 11.0.3
Severity: high
glob CLI: Command injection via -c/--cmd executes matches with shell:true - https://github.com/advisories/GHSA-5j98-mcp5-4vw2
fix available via `npm audit fix`
node_modules/glob
js-yaml 4.0.0 - 4.1.0
Severity: moderate
js-yaml has prototype pollution in merge (<<) - https://github.com/advisories/GHSA-mh29-5h37-fv8m
fix available via `npm audit fix`
node_modules/js-yaml
2 vulnerabilities (1 moderate, 1 high)
To address all issues, run:
npm audit fix
found 0 vulnerabilities
Please select:
Documentation link for docs.joomla.org:
No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | NPM Change |
| Title |
|
||||||
I have tested this item ✅ successfully on 08325f1
| Status | Pending | ⇒ | Ready to Commit |
RTC
| Labels |
Added:
RTC
NPM Resource Changed
bug
PR-6.0-dev
|
||
I have tested this item ✅ successfully on 08325f1
gh pr checkout 46502and runningnpm auditreports 0 vulnerabilitiespackage-lock.jsonfile for comparisation, gone back withgit switch -, didnpm audit fixby own and got exactly the samepackage-lock.jsonfileThis comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46503.