- Server operating system version
- Ubuntu 26.04.1 LTS
- Plesk version and microupdate number
- Plesk Obsidian 18.0.82 Update #3 Web Host Edition
our security scanner flagged multiple extensions from vendor plesk as containing very old composer dependencies.
Plesk extension store shows no updates, latest Obsidian version (18.0.82#3), host os is up to date as well (Ubuntu 26.04.1).
examples:
"Configurations Troubleshooter" shows in `/opt/psa/admin/plib/modules/configurations-troubleshooter/vendor/guzzlehttp/guzzle` a changelog file for "7.9.2 - 2024-07-24".
While there are many newer versions on github guzzle/CHANGELOG.md at 8.5 · guzzle/guzzle, i.e. 7.9.3 or 7.15.1 or even 8.5.2.
There are multiple CVEs reported for the used version. i.e. NVD - Home, OSV - Open Source Vulnerabilities or OSV - Open Source Vulnerabilities
or "name": "guzzlehttp/psr7", "version": "2.7.0",
other extensions like "Sectigo SSL", plib, phpmyadmin/phpmyadmin, "Google Drive Backup" and "WP Toolkit" are in a similar situation.
"WP Toolkit" has "name": "cakephp\/database", "4.6.3", in /vendor/composer/installed.json which is old and contains known security issues.
Why is this?
Are we supposed to run composer update ourself?
Why are patch/bug fix level updates not done at least once a year? Most packages follow semantic versioning, so it should be simple to do.
Even if the security problems are not affecting plesk directly, it would be nice too have them fixed anyways
Thanks
Plesk extension store shows no updates, latest Obsidian version (18.0.82#3), host os is up to date as well (Ubuntu 26.04.1).
examples:
"Configurations Troubleshooter" shows in `/opt/psa/admin/plib/modules/configurations-troubleshooter/vendor/guzzlehttp/guzzle` a changelog file for "7.9.2 - 2024-07-24".
While there are many newer versions on github guzzle/CHANGELOG.md at 8.5 · guzzle/guzzle, i.e. 7.9.3 or 7.15.1 or even 8.5.2.
There are multiple CVEs reported for the used version. i.e. NVD - Home, OSV - Open Source Vulnerabilities or OSV - Open Source Vulnerabilities
or "name": "guzzlehttp/psr7", "version": "2.7.0",
other extensions like "Sectigo SSL", plib, phpmyadmin/phpmyadmin, "Google Drive Backup" and "WP Toolkit" are in a similar situation.
"WP Toolkit" has "name": "cakephp\/database", "4.6.3", in /vendor/composer/installed.json which is old and contains known security issues.
Why is this?
Are we supposed to run composer update ourself?
Why are patch/bug fix level updates not done at least once a year? Most packages follow semantic versioning, so it should be simple to do.
Even if the security problems are not affecting plesk directly, it would be nice too have them fixed anyways
Thanks