CVE-2015-2797
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 AirTies Air 6372, 5760, 5750, 5650TT, 5453, 5444TT, 5443, 5442, 5343, 5342, 5341, and 5021 DSL modems with firmware 1.0.2.0 and earlier allows remote attackers to execute arbitrary code via a long string in the redirect parameter to cgi-bin/login.
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 · high confidenceStack-based buffer overflow in AirTies Air DSL modems allows remote attackers to execute arbitrary code via a crafted redirect parameter to the /cgi-bin/login endpoint. The vulnerability affects multiple AirTies models with firmware 1.0.2.0 and earlier, indicating insufficient input validation on the redirect parameter.
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 data<= 1.0.2.0CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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 AirTies device modelAccess the router web interface or check the device label to confirm it is an AirTies Air DSL modem modelAffected if The device is not an AirTies Air DSL modem - different models are not affected by this specific vulnerability
-
Check firmware versionLog into the router web interface and navigate to the firmware/version information page, or use SNMP or telnet to query the firmware version if availableAffected if Firmware version is 1.0.2.0 or earlier - versions above 1.0.2.0 are not affected
-
Verify /cgi-bin/login endpoint existsAttempt to access http://[router-ip]/cgi-bin/login on the deviceAffected if The endpoint responds, indicating the vulnerable CGI interface is present
-
Confirm remote web interface access is enabledCheck router administration settings for remote management or web interface access from WAN (often labeled as 'Remote Management' or 'Allow access from WAN')Affected if Remote web interface access is enabled - this vulnerability is exploitable remotely when the login page is accessible from the WAN side
The device is affected if it is an AirTies Air DSL modem with firmware version 1.0.2.0 or earlier and the /cgi-bin/login endpoint is accessible remotely.
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 dataPrimary remediation is firmware upgrade to a version beyond 1.0.2.0 from AirTies. If no patch is available, disable remote web interface access or replace affected devices.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2797 — 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-2797 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