CVE-2007-4733
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 Aztech DSL600EU router, when WAN access to the web interface is disabled, does not properly block inbound traffic on TCP port 80, which allows remote attackers to connect to the web interface by guessing a TCP sequence number, possibly involving spoofing of an ARP packet, a related issue to CVE-1999-0077.
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 confidenceThe Aztech DSL600EU router fails to properly block inbound TCP port 80 traffic from the WAN even when WAN access to the web interface is explicitly disabled. Attackers can exploit this by guessing TCP sequence numbers to establish HTTP connections to the router's web interface, potentially combined with ARP spoofing to facilitate the attack.
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 device modelLog into the router's web interface or check the device label to confirm the model is Aztech DSL600EUAffected if The device is an Aztech DSL600EU router (all versions are affected)
-
Verify WAN access setting for web interfaceNavigate to the router's administration settings and check if there is a setting to disable WAN (internet-side) access to the web interface. Note the current state of this setting.Affected if The 'WAN web management' or 'remote management' setting exists and is configured (regardless of whether it is enabled or disabled, since the flaw is that the block does not work)
-
Test TCP port 80 accessibility from WANUse an external system (not on the local network) or an online port scanner to attempt a TCP connection to public IP address on port 80. Alternatively, use a mobile phone on cellular data to visit your public IP address in a browser.Affected if Port 80 responds to WAN connections and displays a router login page, even when WAN web management is supposedly disabled
-
Verify HTTP response from WANIf port 80 is open from WAN, capture the HTTP response to confirm it is the router's web interface (look for Aztech branding or router login prompts)Affected if The HTTP response reveals the router's administration interface to WAN attackers
You are affected if you own an Aztech DSL600EU router and port 80 on your public IP address responds to connections from the internet, revealing the router's web interface regardless of the WAN access control setting.
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 dataSince this is a legacy device from 2007, check for firmware updates from Aztech; if unavailable, replace the device with a current model. As a compensating control, place a firewall in front of the router or implement network segmentation to limit WAN exposure.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4733 — 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-2007-4733 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