CVE-2023-31975
yasm v1.3.0 was discovered to contain a memory leak via the function yasm_intnum_copy at /libyasm/intnum.c.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
yasm v1.3.0 was discovered to contain a memory leak via the function yasm_intnum_copy at /libyasm/intnum.c. Note: Multiple third parties dispute this as a bug and not a vulnerability according to the YASM security policy.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- n/a n/a
Version range not reported
References 18
GitHub · yasm/yasm
openwall.com
- lists/oss-security/2023/06/20/6
- lists/oss-security/2023/06/21/2
- lists/oss-security/2023/06/21/7
- lists/oss-security/2023/06/21/10
- lists/oss-security/2023/06/21/5
- lists/oss-security/2023/06/21/8
- lists/oss-security/2023/06/21/9
- lists/oss-security/2023/06/21/13
- lists/oss-security/2023/06/22/1
- lists/oss-security/2023/06/22/3
- lists/oss-security/2023/06/22/6
- lists/oss-security/2023/06/23/2
- lists/oss-security/2023/06/23/1
- lists/oss-security/2023/06/23/4
- lists/oss-security/2023/06/23/8
- lists/oss-security/2023/06/23/9
- lists/oss-security/2023/06/24/1