CVE-2023-42366

Exp

A heap-buffer-overflow was discovered in BusyBox v.1.36.1 in the next_token function at awk.c:1159.

Published: 2023-11-27 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-42366 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.42%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2023-42366

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2023-42366

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.04% 0.42% +0.37%
2 2025-03-30 0.10% 0.04% -0.06%
3 2025-03-29 — 0.10% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-42366

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2023-42366

OS Trackers for CVE-2023-42366

vendor priority summary link
alpine — CVE-2023-42366: 1 source package rows (busybox); 34 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 29, open 5. https://security.alpinelinux.org/vuln/CVE-2023-42366
debian not yet assigned CVE-2023-42366 not yet assigned priority: Debian including 1 source packages (busybox), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2023-42366
redhat medium — https://access.redhat.com/security/cve/CVE-2023-42366
suse medium CVE-2023-42366 severity moderate: SUSE including 1 source package names (busybox), 1 product×package rows across 1 product lines (SUSE Linux Enterprise Server 11 SP4 LTSS): Known Not Affected 1. https://www.suse.com/security/cve/CVE-2023-42366/
ubuntu medium CVE-2023-42366 medium priority: Ubuntu including 1 source packages (busybox), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needed 7, ignored 4, released 1. https://ubuntu.com/security/CVE-2023-42366

Affected software / configurations for CVE-2023-42366

Vendor Product Version Raw CPE
busybox busybox 1.36.1 cpe:2.3:a:busybox:busybox:1.36.1:*:*:*:*:*:*:*

References for CVE-2023-42366

cvelogic Threat Intelligence