Dire Wolf CVE-2025-34457
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Dire Wolf KISS interface
-
DeliverySend crafted MAX_KISS_LEN frame
-
ExploitOverflow stack appending FEND byte
-
ExecutionOut-of-bounds read in kiss_unwrap
-
ImpactCrash TNC process (DoS)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Trigger requires delivering a crafted KISS frame to Dire Wolf's KISS frame handler (kiss_rec_byte() in src/kiss_frame.c) whose accumulated length reaches MAX_KISS_LEN, leaving no room for the appended terminating FEND byte. Affects versions up to and including 1.8 prior to commit 694c954. The key limiting factor is reachability of a KISS interface: Dire Wolf commonly exposes KISS over a local serial/pseudo-terminal device or a KISS-over-TCP socket, so remote exploitation is realistic only when that TCP KISS port is bound to a network-accessible interface rather than localhost or a trusted RF/serial link. No authentication or user interaction is required once the interface is reachable (PR:N/UI:N), and impact is limited to a crash/denial of service - no confidentiality or integrity loss. |
| Impact | Signals are consistent and point to a genuine but bounded availability risk rather than a top-tier emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated trigger, but impact is strictly availability (VC:N/VI:N/VA:H, SC/SI/SA:N) and CWE-121 plus the description confirm the end state is stack corruption leading to a crash/DoS - not code execution, despite the 'stack-based buffer overflow' label that often implies RCE. EPSS is low (0.51%, 42nd percentile), the CVE is NOT in CISA KEV, and no public exploit is identified in the provided data, so there is no evidence of active or imminent widespread exploitation. The 8.7 'High' score is driven largely by the network/unauthenticated reachability combined with high availability impact; it should be read as a crash/DoS bug, not a remote code execution threat. One caveat to verify: AV:N assumes the KISS interface is network-exposed, but Dire Wolf's KISS access is frequently a local serial/pseudo-terminal or a TCP port that may be bound to localhost or a trusted RF/LAN segment - real exposure depends on deployment, so the practical attack surface may be narrower than AV:N suggests. |
| Exploit ScenarioDerived | An attacker with reach to a Dire Wolf KISS interface (e.g., its KISS-over-TCP port) sends a crafted KISS frame whose length hits MAX_KISS_LEN, so appending the terminating FEND byte overflows the fixed stack buffer. The subsequent kiss_unwrap() call reads/writes out of bounds, corrupting the stack and crashing the Dire Wolf process, dropping the TNC/APRS service. No public proof-of-concept is identified at time of analysis; exploitation is low-complexity (AC:L) and requires no authentication (PR:N) or user interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Denial-of-service in Dire Wolf through version 1.8 occurs when a crafted KISS frame reaches the MAX_KISS_LEN limit, causing kiss_rec_byte() to append a terminating FEND byte without reserving stack space; the resulting out-of-bounds write and subsequent out-of-bounds read in kiss_unwrap() can crash the application. The issue is unauthenticated and remote only when a KISS-over-TCP interface is reachable from an untrusted network, since local serial or RF KISS links are not remotely accessible. No public exploit was identified at time of analysis, EPSS is low at 0.51%, and the assessed impact is availability-only with no confidentiality or integrity loss.
RemediationAI
Apply upstream commit 694c954, or use a later Dire Wolf build that includes it; no tagged release containing the fix was independently confirmed from the provided data, so verify the build includes the kiss_frame.c change before relying on it. If upgrading cannot be done immediately, do not expose the KISS-over-TCP listener to untrusted networks: bind it to localhost or a trusted interface, restrict the port with firewall rules, or disable KISS TCP when it is not needed, accepting that this breaks remote KISS clients. For serial or RF KISS paths, restrict physical and RF access so untrusted parties cannot inject maximum-length KISS frames into the decoder, and monitor the service for crash-restart loops. Consult https://github.com/wb2osz/direwolf/commit/694c954, https://github.com/wb2osz/direwolf/issues/617, and https://www.vulncheck.com/advisories/wb2osz-direwolf-stack-based-buffer-overflow-dos for the vendor and advisory details.
Affected ProductsAI
Dire Wolf (wb2osz/direwolf) versions up to and including 1.8, when built prior to commit 694c954, are affected. No CPE strings were supplied in the input data. Vendor and third-party references include the upstream issue at https://github.com/wb2osz/direwolf/issues/617, the fixing commit at https://github.com/wb2osz/direwolf/commit/694c954, the Marlink Cyber advisory at https://github.com/marlinkcyber/advisories/blob/main/advisories/MCSAID-2025-010-direwolf-stack-buffer-overflow-kiss-frame.md, and the VulnCheck advisory at https://www.vulncheck.com/advisories/wb2osz-direwolf-stack-based-buffer-overflow-dos.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Dire Wolf implements the KISS protocol used to carry AX.25 packet-radio frames over serial links or TCP sockets, with FEND and FESC byte framing handled in src/kiss_frame.c. The CWE-121 stack-based buffer overflow arises in kiss_rec_byte(): while in the KS_COLLECTING state, the function accepts non-FEND bytes up to MAX_KISS_LEN, then appends the terminating FEND without ensuring the stack buffer has room for that extra byte. This out-of-bounds write is followed by an out-of-bounds read when the malformed frame is passed to kiss_unwrap(), producing stack corruption or a crash. The upstream fix in commit 694c954 adjusts the collection limit and enlarges the unwrapped stack buffer to MAX_KISS_LEN; exploitation is bounded by whether the KISS interface is exposed over TCP rather than confined to localhost, serial, or trusted RF links.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Unauthenticated low-complexity frame sent to the network-reachable KISS handler (AV:N/AC:L/PR:N/UI:N); only a crash results, so C:N/I:N/A:H with no scope change.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
wb2osz/direwolf (Dire Wolf) versions up to and including 1.8, prior to commit 694c954, contain a stack-based buffer overflow vulnerability in the function kiss_rec_byte() located in src/kiss_frame.c. When processing crafted KISS frames that reach the maximum allowed frame length (MAX_KISS_LEN), the function appends a terminating FEND byte without reserving sufficient space in the stack buffer. This results in an out-of-bounds write followed by an out-of-bounds read during the subsequent call to kiss_unwrap(), leading to stack memory corruption or application crashes. This vulnerability may allow remote unauthenticated attackers to trigger a denial-of-service condition.
Executive ViewAI
Dire Wolf, the software soundcard TNC and APRS package used for radio-based data communications, is affected through version 1.8 by a memory-handling defect in which a single malformed KISS frame can crash the running application, making this an availability-only exposure with no risk to data confidentiality or integrity. The realistic attack surface is limited to deployments that expose a KISS-over-TCP interface to an untrusted network, since local serial and RF KISS links are not remotely reachable. With no vendor-released patch and no public exploit code identified, leadership should treat this as a moderate, exposure-dependent availability risk to any radio, telemetry, or APRS service that relies on Dire Wolf and to the operational response effort of restarting it after a crash.
No vendor-released patch identified at time of analysis; interim mitigations are to restrict KISS-over-TCP listeners to trusted hosts via firewall rules or ACLs, disable the KISS-over-TCP interface where it is not operationally required and use serial or RF links instead, segment Dire Wolf hosts from untrusted networks, and run the service under supervision with crash alerting and automatic restart to limit downtime.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
NVD
CVE.org
EPSS
GitHub
Exploit-DB