# CVE-2004-2427: Missing authorization in n/a

> Remote attackers can access sensitive data, modify system settings, or cause a reboot on Axis cameras and video servers without 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:** 18 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-ffg4-rw8m-pqqv

## What is CVE-2004-2427?

CVE-2004-2427 is a critical missing authorization vulnerability in n/a, published on 18 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Axis Network Camera 2.40 and earlier, and Video Server 3.12 and earlier, allows remote attackers to obtain sensitive information via direct requests to (1) admin/getparam.cgi, (2) admin/systemlog.cgi, (3) admin/serverreport.cgi, and (4) admin/paramlist.cgi, modify system information via (5) setparam.cgi and (6) factorydefault.cgi, or (7) cause a denial of service (reboot) via restart.cgi.

## Which versions are affected by CVE-2004-2427?

It affects 14 products.


Products: Axis 2100 Network Camera, Axis 2110 Network Camera, Axis 2120 Network Camera, Axis 2130 Ptz Network Camera, Axis 230 Mpeg2 Video Server, Axis 2400 Video Server, Axis 2401 Video Server, Axis 2411 Video Server, Axis 2420 Network Camera, Axis 2420 Video Server, Axis 2460 Network Dvr, Axis 2490 Serial Server, Axis 250s Video Server, Axis Storpoint Cd.

## How do I fix CVE-2004-2427?

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

## Is CVE-2004-2427 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0240](https://insights.sbomify.com/CVE-2003-0240/): Auth bypass in n/a (critical 10.0)
- [CVE-2007-5213](https://insights.sbomify.com/CVE-2007-5213/): Cross-site request forgery in n/a (critical 9.3)
- [CVE-2007-2239](https://insights.sbomify.com/CVE-2007-2239/): Memory corruption in n/a (critical 9.3)
- [CVE-2004-2425](https://insights.sbomify.com/CVE-2004-2425/): Command injection in n/a (high 7.5)
- [CVE-2001-1543](https://insights.sbomify.com/CVE-2001-1543/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2427 and fix it if it is affected.

What it is: CVE-2004-2427 is a critical missing authorization vulnerability in n/a, published on 18 Aug 2005. 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-2004-2427 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-2004-2427/ (Markdown: https://insights.sbomify.com/CVE-2004-2427/index.md)
```

## Sources

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

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