Process crash via unchecked interface-name copy
Published Dec 16, 2024 · Updated Apr 3, 2025
Stack buffer overflow in iptraf-ng 1.2.1 allows local users to crash the process via an overlong interface name. Functions in src/ifaces.c copy a user-supplied interface name with strcpy into fixed-size ifreq fields without checking its length. Triggering requires control of an iptraf-ng interface-name argument; compiler hardening limits the reported consequence to a process crash.
Summary
What happened
Stack buffer overflow in iptraf-ng 1.2.1 allows local users to crash the process via an overlong interface name. Functions in src/ifaces.c copy a user-supplied interface name with strcpy into fixed-size ifreq fields without checking its length. Triggering requires control of an iptraf-ng interface-name argument; compiler hardening limits the reported consequence to a process crash.
The record
- CVE
- CVE-2024-52949
- Published
- Dec 16, 2024
- Updated
- Apr 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2024CVE publishedPublication date reported by the CVE source.
- Apr 3, 2025Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Gruppo TIM iptraf-ng proof of conceptproof of concept · unverified
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