CVE-2011-1326
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 · uneditedUnspecified vulnerability on the La Fonera+ router with firmware before 1.7.0.1 allows remote attackers to cause a denial of service via unknown vectors.
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 confidenceRemote denial of service vulnerability in La Fonera+ router firmware versions prior to 1.7.0.1. The vulnerability is remotely exploitable without authentication and allows attackers to cause device unavailability via unspecified vectors.
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.1.2.1= 1.1.1.1= 1.1.1.2all 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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:A/AC:L/Au:N/C:N/I:N/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 modelCheck the device label or access the web administration interface at http://192.168.1.1 and look for the model name 'La Fonera+' or 'Fon La Fonera+'Affected if The device is not a La Fonera+ router, then this CVE does not apply
-
Check the firmware version via web interfaceLog into the router web interface and navigate to the 'Status' or 'System' page to view the installed firmware versionAffected if The displayed firmware version is less than 1.7.0.1, or if it shows a version matching <= 1.1.2.1, = 1.1.1.1, or = 1.1.1.2, the device is affected
-
Check the firmware version via SSH/TelnetConnect to the router via SSH or Telnet (if enabled) and run the command 'cat /etc/firmware_version' or 'nvram get firmware_version' to retrieve the installed versionAffected if The command output shows a version lower than 1.7.0.1, or shows one of the specifically listed affected versions
-
Check the firmware version via UPnPSend a UPnP request to the router and inspect the 'Server: Linux/2.6 XX' header or the model description for version informationAffected if The version information obtained indicates a firmware below 1.7.0.1
The device is affected if it is a La Fonera+ router running firmware version 1.7.0.1 or later is NOT installed, particularly if the version is <= 1.1.2.1, = 1.1.1.1, = 1.1.1.2, or any version before 1.7.0.1 since the listing indicates all versions may be vulnerable.
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 dataUpdate La Fonera+ firmware to version 1.7.0.1 or later to remediate the vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1326 — 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-2011-1326 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