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

> Remote attackers can execute arbitrary code on Huawei routers and switches via a stack-based buffer overflow in the HTTP module.

- **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:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2013
- **Updated:** 17 Sep 2024
- **Also known as:** CVE-2012-4965, GHSA-56jr-5rr7-hg8x

## What is CVE-2012-6569?

CVE-2012-6569 is a critical memory corruption vulnerability in n/a, published on 20 Jun 2013. 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 HTTP module in the (1) Branch Intelligent Management System (BIMS) and (2) web management components on Huawei AR routers and S2000, S3000, S3500, S3900, S5100, S5600, S7800, and S8500 switches allows remote attackers to execute arbitrary code via a long URI.

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

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

It affects 18 products.


Products: Huawei Ar 18-1x, Huawei Ar 18-2x, Huawei Ar 18-3x, Huawei Ar 19\/29\/49, Huawei Ar 28\/46, Huawei S2000, Huawei S2300, Huawei S2700, Huawei S3000, Huawei S3300, Huawei S3300hi, Huawei S3500, Huawei S3700, Huawei S3900, Huawei S5100, Huawei S5600, Huawei S7800, Huawei S8500.

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

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

## Is CVE-2012-6569 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6570](https://insights.sbomify.com/CVE-2012-6570/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-6571](https://insights.sbomify.com/CVE-2012-6571/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-6569 is a critical memory corruption vulnerability in n/a, published on 20 Jun 2013. 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-2012-6569 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-2012-6569/ (Markdown: https://insights.sbomify.com/CVE-2012-6569/index.md)
```

## Sources

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

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