Akw D800Hardware / appliance · Axesstel

CVE-2008-3411

HIGH · 10.0 CVSS v2.0 Published 2008-07-31

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The Axesstel AXW-D800 modem with D2_ETH_109_01_VEBR Jun-14-2006 software does not require authentication for (1) etc/config/System.html, (2) etc/config/Network.html, (3) etc/config/Security.html, (4) cgi-bin/sysconf.cgi, and (5) cgi-bin/route.cgi, which allows remote attackers to change the modem's configuration via direct requests.

Technical summary

dbcve analysis · high confidence

The Axesstel AXW-D800 modem running D2_ETH_109_01_VEBR firmware fails to enforce authentication on five critical configuration endpoints: System.html, Network.html, Security.html, sysconf.cgi, and route.cgi. An unauthenticated remote attacker can directly access these paths to modify modem settings, potentially gaining full control over the device and network configuration.

MitigationEnable authentication on the affected configuration pages and CGI scripts, or apply vendor firmware updates if available. If the device cannot be patched, consider network segmentation to limit exposure and monitor for unauthorized configuration changes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Akw D800Hardware / appliance

Affected:= d2_eth_109_01_vebr

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify the device model

Check the modem label or access the web interface to confirm the model is Axesstel AXW-D800 or Akw D800

Affected if Device model is Axesstel AXW-D800 or Akw D800
Verify firmware version

Access the modem web interface and check the firmware version, typically visible on the main status page or System.html

Affected if Firmware version equals d2_eth_109_01_vebr
Test unauthenticated access to System.html

Using a web browser or curl, attempt to access http://<modem_ip>/System.html without providing any login credentials

Affected if The page loads and displays modem system configuration without requiring authentication
Test unauthenticated access to Network.html

Using a web browser or curl, attempt to access http://<modem_ip>/Network.html without providing any login credentials

Affected if The page loads and displays network configuration without requiring authentication
Test unauthenticated access to Security.html

Using a web browser or curl, attempt to access http://<modem_ip>/Security.html without providing any login credentials

Affected if The page loads and displays security settings without requiring authentication
Test unauthenticated access to sysconf.cgi and route.cgi

Using a web browser or curl, attempt to access http://<modem_ip>/sysconf.cgi and http://<modem_ip>/route.cgi without providing any login credentials

Affected if The CGI scripts execute or return configuration data without requiring authentication

You are affected if you have an Axesstel AXW-D800 or Akw D800 modem running firmware version d2_eth_109_01_vebr and any of the five endpoints are accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Enable authentication on the affected configuration pages and CGI scripts, or apply vendor firmware updates if available. If the device cannot be patched, consider network segmentation to limit exposure and monitor for unauthorized configuration changes.

Fix this in Akw D800 Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get help mitigating

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 locally

dbcve dependency scanner

Check whether your project pulls in CVE-2008-3411 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-3411 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2008-3411?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 2.6%

Affects: Akw D800

Remediation

A high-priority fix

Fix this in Akw D800 18 hrs · Moderate

Typical engagement from $3,200

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2008-3411 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References