CVE-2007-0193
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 · uneditedFON La Fonera routers do not properly limit DNS service access by unauthenticated clients, which allows remote attackers to tunnel traffic via DNS requests for hosts that should not be accessible before authentication.
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 confidenceFON La Fonera routers expose DNS service to unauthenticated clients, allowing remote attackers to tunnel arbitrary traffic through DNS requests to reach internal hosts that should require authentication.
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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 the device is a Fon La Fonera routerCheck the router model number, firmware, or web interface for 'La Fonera' or 'Fon' branding. The device is typically a small wireless router with FON branding.Affected if The device is a Fon La Fonera router - all versions are affected.
-
Determine if DNS service is running on the routerAccess the router's web interface or use command line tools (if accessible) to check if the DNS proxy service is enabled. Look for DNS settings, DNS forwarder, or DNS proxy options in the router configuration.Affected if DNS service is enabled on the router.
-
Verify DNS accessibility from untrusted networksFrom a client not on the trusted internal network (e.g., from WAN side or a separate untrusted network), attempt to query the router's IP address on port 53 (DNS). Use a tool like 'nslookup' or 'dig' pointing to the router's IP.Affected if DNS queries to the router's IP address succeed from untrusted/unauthenticated clients.
-
Check if DNS service allows unauthenticated accessReview the router's DNS service configuration to determine if any authentication, ACL, or access restrictions are required before DNS queries can be processed.Affected if No authentication or access control is required to use the DNS service.
If you operate a Fon La Fonera router with DNS service enabled and that service is accessible to unauthenticated clients from untrusted networks, your environment is affected by this vulnerability.
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 dataImplement access control lists or authentication requirements on the DNS service to restrict access to authenticated users only, or upgrade to a patched firmware version.
- 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-2007-0193 — 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-0193 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