# CVE-2014-7249: Memory corruption in n/a

> Remote attackers can execute arbitrary code on Allied Telesis network devices via a crafted HTTP POST request due to a buffer overflow.

- **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:** 19 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r2p3-v7r6-vhc6

## What is CVE-2014-7249?

CVE-2014-7249 is a critical memory corruption vulnerability in n/a, published on 19 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow on the Allied Telesis AR440S, AR441S, AR442S, AR745, AR750S, AR750S-DP, AT-8624POE, AT-8624T/2M, AT-8648T/2SP, AT-8748XL, AT-8848, AT-9816GB, AT-9924T, AT-9924Ts, CentreCOM AR415S, CentreCOM AR450S, CentreCOM AR550S, CentreCOM AR570S, CentreCOM 8700SL, CentreCOM 8948XL, CentreCOM 9924SP, CentreCOM 9924T/4SP, Rapier 48i, and SwitchBlade4000 with firmware before 2.9.1-21 allows remote attackers to execute arbitrary code via a crafted HTTP POST request.

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

## Which versions are affected by CVE-2014-7249?

It affects 48 products.


Products: Alliedtelesis Ar440s, Alliedtelesis Ar440s Firmware, Alliedtelesis Ar441s, Alliedtelesis Ar441s Firmware, Alliedtelesis Ar442s, Alliedtelesis Ar442s Firmware, Alliedtelesis Ar745, Alliedtelesis Ar745 Firmware, Alliedtelesis Ar750s, Alliedtelesis Ar750s-Dp, Alliedtelesis Ar750s-Dp Firmware, Alliedtelesis Ar750s Firmware, Alliedtelesis At-8624poe, Alliedtelesis At-8624poe Firmware, Alliedtelesis At-8624t\/2m, Alliedtelesis At-8624t\/2m Firmware, Alliedtelesis At-8648t\/2sp, Alliedtelesis At-8648t\/2sp Firmware, Alliedtelesis At-8748xl, Alliedtelesis At-8748xl Firmware and 28 more.

## How do I fix CVE-2014-7249?

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

## Is CVE-2014-7249 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-7249 and fix it if it is affected.

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

## Sources

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

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