CVE-2015-6949
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 · uneditedStack-based buffer overflow in the ASUS TM-AC1900 router allows remote attackers to execute arbitrary code via crafted HTTP header values.
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-based buffer overflow vulnerability exists in the ASUS TM-AC1900 router's HTTP server component. The vulnerability is triggered by sending specially crafted HTTP header values that exceed expected buffer boundaries, allowing an attacker to overwrite stack memory and potentially execute arbitrary code remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS 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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 the router modelLog into the router admin interface or check the device label to confirm the exact model number is ASUS TM-AC1900Affected if The device is an ASUS TM-AC1900 router, as all firmware versions are affected
-
Check firmware versionIn the router admin panel, navigate to the Firmware Version or System Information page. Compare the displayed version against any available patched versions from ASUS support.Affected if Any firmware version is installed on the TM-AC1900, as all versions are vulnerable
-
Verify HTTP management is enabledIn the router admin interface, go to WAN or Remote Management settings. Check if HTTP/HTTPS remote management or the Web GUI is exposed to the WAN/internet.Affected if Remote HTTP management or the web interface is enabled and accessible from the WAN side, making the router exploitable over the network
-
Check exposed network servicesUse an external port scanner to test if ports 80 (HTTP) or 443 (HTTPS) are open and responding on the router's WAN IP address.Affected if Port 80 or 443 is open and reachable from the internet on the router's public IP, indicating the vulnerable HTTP server is exposed
-
Confirm internal network exposureIf remote management is disabled externally, verify if the HTTP server is still accessible from the local network by accessing the router's LAN IP via HTTP.Affected if The HTTP server is accessible from any network segment beyond the trusted admin workstation, as the vulnerability exists in the server component itself
You are affected if you own an ASUS TM-AC1900 router and its HTTP server component is accessible from any network where an attacker could send malicious HTTP headers.
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 dataApply the vendor-supplied firmware patch when available. If no patch exists, consider network segmentation to limit exposure and disable remote management interfaces until a fix can be deployed.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6949 — 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-2015-6949 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