# CVE-2008-1491: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the ASUS Remote Console DPC Proxy server.

- **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:** 25 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9jrf-fg4x-fj2v

## What is CVE-2008-1491?

CVE-2008-1491 is a critical memory corruption vulnerability in n/a, published on 25 Mar 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in the DPC Proxy server (DpcProxy.exe) in ASUS Remote Console (aka ARC or ASMB3) 2.0.0.19 and 2.0.0.24 allows remote attackers to execute arbitrary code via a long string to TCP port 623.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-1491?

It affects 1 product.


Products: Asus Remote Console.

## How do I fix CVE-2008-1491?

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

## Is CVE-2008-1491 being exploited?

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

Public exploit code:

- Asus Dpcproxy Buffer Overflow (metasploit)
- ASUS DPC Proxy 2.0.0.16/19 - Remote Buffer Overflow (exploitdb)
- Asus Dpcproxy - Remote Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1491 and fix it if it is affected.

What it is: CVE-2008-1491 is a critical memory corruption vulnerability in n/a, published on 25 Mar 2008. 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-2008-1491 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-2008-1491/ (Markdown: https://insights.sbomify.com/CVE-2008-1491/index.md)
```

## Sources

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

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