sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| sparklemotion | sqlite3-ruby | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Sparklemotion | Sqlite3-ruby |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-28hh-pr2h-2w89 | sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.142% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-825 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sparklemotion
Sparklemotion sqlite3-ruby |
|
| Vendors & Products |
Sparklemotion
Sparklemotion sqlite3-ruby |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version 2.9.5. | |
| Title | sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity | |
| Weaknesses | CWE-416 | |
| References |
|
|
| Metrics |
cvssV4_0
|