CVE-2023-51258
CVE-2023-51258 is a medium-severity vulnerability in Tortall Yasm with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-401.
Key facts
- Severity: Medium (CVSS 3.x base score 5.5)
- EPSS exploit prediction: 0% (17th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2023-55980
- Weakness: CWE-401
- Affected product: Tortall Yasm
- Published:
- Last modified:
Description
A memory leak issue discovered in YASM v.1.3.0 allows a local attacker to cause a denial of service via the new_Token function in the modules/preprocs/nasm/nasm-pp:1512.
Frequently asked questions
- What is CVE-2023-51258?
- A memory leak issue discovered in YASM v.1.3.0 allows a local attacker to cause a denial of service via the new_Token function in the modules/preprocs/nasm/nasm-pp:1512.
- How severe is CVE-2023-51258?
- CVE-2023-51258 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
- Is CVE-2023-51258 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2023-51258?
- CVE-2023-51258 affects Tortall Yasm. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2023-51258?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2023-51258 have an EU (EUVD) identifier?
- Yes. CVE-2023-51258 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2023-55980.
- When was CVE-2023-51258 published?
- CVE-2023-51258 was published on 2024-01-18 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:tortall:yasm:1.3.0:*:*:*:*:*:*:*
More vulnerabilities in Tortall Yasm
- CVE-2023-31973 — Medium (CVSS 5.5): yasm v1.3.0 was discovered to contain a use after free via the function expand_mmac_params at /nasm/nasm-pp.c. Note:…
- CVE-2023-31974 — Medium (CVSS 5.5): yasm v1.3.0 was discovered to contain a use after free via the function error at /nasm/nasm-pp.c. Note: Multiple third…
- CVE-2023-31972 — Medium (CVSS 5.5): yasm v1.3.0 was discovered to contain a use after free via the function pp_getline at /nasm/nasm-pp.c. Note: Multiple…
- CVE-2021-33468 — Medium (CVSS 5.5): An issue was discovered in yasm version 1.3.0. There is a use-after-free in error() in modules/preprocs/nasm/nasm-pp.c.
- CVE-2021-33467 — Medium (CVSS 5.5): An issue was discovered in yasm version 1.3.0. There is a use-after-free in pp_getline() in…
- CVE-2021-33466 — Medium (CVSS 5.5): An issue was discovered in yasm version 1.3.0. There is a NULL pointer dereference in expand_smacro() in…
All CVEs affecting Tortall Yasm →
Other CWE-401 (Missing Release of Memory after Effective Lifetime) vulnerabilities
- CVE-2026-46289 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: lib/scatterlist: fix length calculations in…
- CVE-2022-0742 — Critical (CVSS 9.1): Memory leak in icmp6 implementation in Linux Kernel 5.13+ allows a remote attacker to DoS a host by making it go…
- CVE-2024-25450 — High (CVSS 8.8): imlib2 v1.9.1 was discovered to mishandle memory allocation in the function init_imlib_fonts().
- CVE-2023-33718 — High (CVSS 8.8): mp4v2 v2.1.3 was discovered to contain a memory leak via MP4File::ReadString() at mp4file_io.cpp
- CVE-2021-40633 — High (CVSS 8.8): A memory leak (out-of-memory) in gif2rgb in util/gif2rgb.c in giflib 5.1.4 allows remote attackers trigger an out of…
- CVE-2021-3492 — High (CVSS 8.8): Shiftfs, an out-of-tree stacking file system included in Ubuntu Linux kernels, did not properly handle faults occurring…
Browse all CWE-401 (Missing Release of Memory after Effective Lifetime) vulnerabilities →