Content Sync (content-sync.io)
The module does not properly scramble the password of the system user that synchronises content. Someone with access to the database could see this password and use it to change or add data. They could not do this without already having access to the database.
- Who could do thisOnly someone with an administrator login.
- Does it apply to youAn attacker has a copy of the database or can read the user data table directly.
- Has it been used in attacksNo sign of it.
- How urgentDrupal rates this moderately critical. Include it in your next routine update, within the month.
Tell your developerUpdate Content Sync (content-sync.io) to 3.2.2.
For developers: what the fix changed
The fix replaces a hardcoded default encryption key with a site-specific key generated using `random_bytes()` and stored in the site's state storage. This is implemented by introducing a new `StateKeyProvider` in `src/Plugin/KeyProvider/StateKeyProvider.php` and updating the installation and update hooks in `cms_content_sync.install` to generate and use this new key.
Also in this release The release also updates the changelog.
CHANGELOG.md+3 −0cms_content_sync.info.yml+1 −0 fixcms_content_sync.install+192 −2 fixcms_content_sync.module+25 −0 fixconfig/install/key.key.cms_content_sync.yml+5 −8 fixconfig/schema/cms_content_sync.schema.yml+5 −0 fixsrc/Plugin/KeyProvider/StateKeyProvider.php+98 −0 fix