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

> Remote attackers can gain administrative privileges on ELSA Lancom 1100 Office devices because the web administration server lacks authentication.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-p2gm-3rxf-q5hf

## What is CVE-2001-1223?

CVE-2001-1223 is a critical missing authorization vulnerability in n/a, published on 15 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web administration server for ELSA Lancom 1100 Office does not require authentication, which allows arbitrary remote attackers to gain administrative privileges by connecting to the server.

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

It affects 1 product.


Products: Elsa Lancom 1100 Office.

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

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

## Is CVE-2001-1223 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1223 is a critical missing authorization vulnerability in n/a, published on 15 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-1223 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-1223/ (Markdown: https://insights.sbomify.com/CVE-2001-1223/index.md)
```

## Sources

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

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