# CVE-2012-2426: Null dereference in n/a

> Remote attackers can crash the xArrow server via a NULL pointer dereference, causing a denial of service.

- **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:** 25 May 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4fh8-93gg-2hw6

## What is CVE-2012-2426?

CVE-2012-2426 is a high-severity vulnerability in n/a, published on 25 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The server in xArrow before 3.4.1 does not properly allocate memory, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via unspecified vectors.

Weakness: CWE-399

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

It affects 1 product.


Products: Xarrow Xarrow.

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

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

## Is CVE-2012-2426 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2427](https://insights.sbomify.com/CVE-2012-2427/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-2428](https://insights.sbomify.com/CVE-2012-2428/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2429](https://insights.sbomify.com/CVE-2012-2429/): Memory corruption in n/a (critical 10.0)
- [CVE-2021-33001](https://insights.sbomify.com/CVE-2021-33001/): xArrow SCADA Cross-site Scripting (medium 6.1)
- [CVE-2021-33021](https://insights.sbomify.com/CVE-2021-33021/): xArrow SCADA Cross-site Scripting (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2426 is a high-severity vulnerability in n/a, published on 25 May 2012. 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-2426 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-2426/ (Markdown: https://insights.sbomify.com/CVE-2012-2426/index.md)
```

## Sources

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

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