CVE-2021-30218 json
samurai 1.2 has a NULL pointer dereference in writefile() in util.c via a crafted build file.
published 2021-04-29 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-17150
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
samurai 1.2 has a NULL pointer dereference in writefile() in util.c via a crafted build file.
Patch / fix
- samurai Alpine 3.24, Alpine 3.23, Alpine 3.22 +9 more 1.2-r1
alpine advisories ALPINE-CVE-2021-30218
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2021-30218 updated cvss 4.7
samurai: NULL pointer dereference in writefile() in util.c
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/michaelforney/samurai/issues/67 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
github.com
/michaelforney/samurai/commit/e84b6d99c85043fa1ba54851ee500540ec206918
patch, third-party-advisory
-
github.com
/michaelforney/samurai/issues/67
exploit, issue-tracking, third-party-advisory
Sources
- CVE List CVE-2021-30218
- NVD CVE-2021-30218
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.