Build process crash via NULL command dereference
Published Apr 29, 2021 · Updated Aug 3, 2024
A NULL pointer dereference in samurai 1.2 allows local users to crash the active build process via a crafted build file. The parser accepts an empty command value, so printstatus() substitutes the resulting NULL command pointer for an absent description and passes it to puts(). Execution requires a user to run samurai against the crafted file, terminating that build invocation without reported confidentiality or integrity impact.
Summary
What happened
A NULL pointer dereference in samurai 1.2 allows local users to crash the active build process via a crafted build file. The parser accepts an empty command value, so printstatus() substitutes the resulting NULL command pointer for an absent description and passes it to puts(). Execution requires a user to run samurai against the crafted file, terminating that build invocation without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2021-30219
- Published
- Apr 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 68 reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo