# CVE-2001-1484: Missing authorization in n/a

> Remote attackers on the LAN can modify firmware and configuration via unauthenticated TFTP access on Alcatel ADSL modems.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v63c-22gx-p9cv

## What is CVE-2001-1484?

CVE-2001-1484 is a high-severity missing authorization vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Alcatel ADSL modems allow remote attackers to access the Trivial File Transfer Protocol (TFTP) to modify firmware and configuration via a bounce attack from a system on the local area network (LAN) side, which is allowed to access TFTP without authentication.

## Which versions are affected by CVE-2001-1484?

It affects 2 products.


Products: Alcatel Adsl Modem 1000, Alcatel Speed Touch Adsl Modem.

## How do I fix CVE-2001-1484?

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

## Is CVE-2001-1484 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1484 and fix it if it is affected.

What it is: CVE-2001-1484 is a high-severity missing authorization vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-1484 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-2001-1484/ (Markdown: https://insights.sbomify.com/CVE-2001-1484/index.md)
```

## Sources

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

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