stigmem Plugin Signature Enforcement Bypass via Configuration
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| eidetic-labs | stigmem | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Eidetic-labs | Stigmem |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.115% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eidetic-labs
Eidetic-labs stigmem |
|
| Vendors & Products |
Eidetic-labs
Eidetic-labs stigmem |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | stigmem-node 0.9.0a1 allows plugin signature enforcement to be disabled via a single configuration flag without a second explicit acknowledgment. If that setting is carried into an environment where plugin directories are writable by less-trusted users, unsigned (potentially malicious) plugin code could be loaded and executed, resulting in arbitrary code execution. Fixed in 0.9.0a2, which requires a second explicit acknowledgment to disable signature enforcement. | |
| Title | stigmem Plugin Signature Enforcement Bypass via Configuration | |
| Weaknesses | CWE-494 | |
| References |
| |
| Metrics |
cvssV4_0
|