What is the Vulnerability?

A single configuration flag in stigmem-node could disable plugin signature enforcement. If an operator unintentionally carried this setting into an environment where plugin paths are writable by less-trusted users, unsigned plugin code could be loaded.

Impact and Risks

The impact of this vulnerability is that it could allow unsigned plugin code to be executed, potentially leading to security breaches. This is particularly concerning in shared or production environments where multiple users have access.

How was the Vulnerability Patched?

The vulnerability was patched in version 0.9.0a2 of stigmem-node. The key change is that disabling plugin signature enforcement now requires a second explicit acknowledgment value, adding an extra layer of protection against unintentional exposure.

Workarounds Before Upgrading

Before upgrading to the patched version, users can follow these workarounds to mitigate the risk:
  • Keep plugin signing required in all shared or production environments.
  • Ensure plugin directories are not writable by untrusted users.

Upgrading to the Patched Release

To upgrade to the patched release, users can run the following command: 
pip install --upgrade --pre stigmem-node
For developers installing through the Stigmem meta-package, the command is: 
pip install --upgrade --pre 'stigmem[node]'

Additional Resources

For more information, users can refer to the following resources:
  • Release: https://github.com/eidetic-labs/stigmem/releases/tag/v0.9.0a2
  • Changelog: https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/CHANGELOG.md#L14-L35
  • Security policy and posture: https://github.com/eidetic-labs/stigmem/blob/v0.9.0a2/SECURITY.md