# CVE-2009-2305: Denial of service in n/a

> Remote attackers can cause denial of service on ARD-9808 DVR security cameras by sending a specially crafted long URI.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 2 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7q4w-gjvp-92qw

## What is CVE-2009-2305?

CVE-2009-2305 is a high-severity denial of service vulnerability in n/a, published on 2 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ARD-9808 DVR card security camera allows remote attackers to cause a denial of service via a long URI composed of //.\ (slash slash dot backslash) sequences.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2009-2305?

It affects 2 products.


Products: Armassa Ard-9808, Armassa Ard-9808 Software.

## How do I fix CVE-2009-2305?

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

## Is CVE-2009-2305 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2305 exists.

Public exploit code:

- ARD-9808 DVR Card Security Camera - GET Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2306](https://insights.sbomify.com/CVE-2009-2306/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2305 and fix it if it is affected.

What it is: CVE-2009-2305 is a high-severity denial of service vulnerability in n/a, published on 2 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2305 exists.

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-2009-2305/ (Markdown: https://insights.sbomify.com/CVE-2009-2305/index.md)
```

## Sources

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

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