# CVE-2012-4924: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in the ASUS Net4Switch ActiveX component, requiring user interaction to trigger the vulnerable method.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ww3r-35r8-mxqp

## What is CVE-2012-4924?

CVE-2012-4924 is a critical memory corruption vulnerability in n/a, published on 15 Sep 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the CxDbgPrint function in the ipswcom.dll ActiveX component 1.0.0.1 for ASUS Net4Switch 1.0.0020 allows remote attackers to execute arbitrary code via a long parameter to the Alert method.

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

## Which versions are affected by CVE-2012-4924?

It affects 2 products.


Products: Asus Ipswcom Activex Component, Asus Net4switch.

## How do I fix CVE-2012-4924?

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

## Is CVE-2012-4924 being exploited?

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

Public exploit code:

- ASUS Net4Switch ipswcom.dll ActiveX Stack Buffer Overflow (metasploit)
- ASUS Net4Switch - 'ipswcom.dll' ActiveX Stack Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4924 and fix it if it is affected.

What it is: CVE-2012-4924 is a critical memory corruption vulnerability in n/a, published on 15 Sep 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4924 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-2012-4924/ (Markdown: https://insights.sbomify.com/CVE-2012-4924/index.md)
```

## Sources

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

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