CVE-2024-6198
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe device exposes a web interface on ports TCP/3030 and TCP/9882. This web service runs lighttpd, which implements the “SNORE” interface. This interface is affected by a stack buffer overflow vulnerability due to insecure path parsing. An attacker with access to the LAN network interface could use a specially crafted HTTP request to exploit a buffer overflow on the modem.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stack buffer overflow vulnerability exists in the lighttpd web server's 'SNORE' interface on TCP ports 3030 and 9882. The flaw is caused by insecure path parsing, allowing an attacker with LAN access to send specially crafted HTTP requests that can overflow the stack and potentially execute arbitrary code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- None
- Authentication
- Y
- User interaction
- None
- Scope
- N
CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:U/V:C/RE:M/U:Red
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if lighttpd is installedRun 'lighttpd -v' or check for the binary at /usr/sbin/lighttpd, or use package manager query like 'dpkg -l | grep lighttpd' or 'rpm -qa | grep lighttpd'Affected if lighttpd is present on the system
-
Determine lighttpd versionExecute 'lighttpd -v' and note the version number, or check via package managerAffected if version is within the affected range and the vendor has not issued a fixed version
-
Check if ports 3030 or 9882 are listeningRun 'netstat -tlnp | grep -E "3030|9882"' or 'ss -tlnp | grep -E "3030|9882"' to see if these ports are open and boundAffected if either TCP port 3030 or 9882 is listening, indicating the SNORE interface may be active
-
Inspect lighttpd configuration for SNORE moduleReview lighttpd.conf (commonly at /etc/lighttpd/lighttpd.conf or /etc/lighttpd/conf.d/) for lines loading the 'mod_snore' or similar module, and check for port bindings 3030 or 9882Affected if the SNORE module is loaded and bound to the vulnerable ports
-
Verify network exposure of the SNORE portsCheck firewall rules with 'iptables -L' or 'ufw status', and test external accessibility from an untrusted network using 'nmap -p 3030,9882 <external-ip>'Affected if ports 3030 or 9882 are accessible from untrusted networks or the internet
A system is affected if it runs a vulnerable lighttpd version with the SNORE interface enabled on ports 3030 or 9882 and those ports are accessible to untrusted LAN or external attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network access to ports 3030 and 9882 via firewall rules or network segmentation to limit exposure to trusted LAN hosts only. Apply vendor firmware updates when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6198 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data