# CVE-2011-1326: Denial of service in n/a

> Remote attackers can cause a denial of service on La Fonera+ routers via unspecified vectors, requiring firmware updates.

- **Severity:** Medium 6.1 (`AV:A/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-37j2-4mf7-p7r4

## What is CVE-2011-1326?

CVE-2011-1326 is a medium-severity denial of service vulnerability in n/a, published on 13 May 2011. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified 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.

## Which versions are affected by CVE-2011-1326?

It affects 2 products.


Products: Fon La Fonera\+, Fon La Fonera\+ Firmware.

## How do I fix CVE-2011-1326?

No fix has been published for CVE-2011-1326 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-1326 being exploited?

There is no known exploitation of CVE-2011-1326 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1326 and fix it if it is affected.

What it is: CVE-2011-1326 is a medium-severity denial of service vulnerability in n/a, published on 13 May 2011. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1326 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-1326/ (Markdown: https://insights.sbomify.com/CVE-2011-1326/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-1326
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-1326
- OSV: https://osv.dev/vulnerability/CVE-2011-1326

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-1326/
Summaries are generated and may contain mistakes; the official description above is the record.