# CVE-2010-1612: Denial of service in n/a

> Remote attackers can cause a denial of service on IBM SOA Appliances using QLOGIC interfaces by sending malformed ICMP packets.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cw5g-6vjh-8wpg

## What is CVE-2010-1612?

CVE-2010-1612 is a medium-severity denial of service vulnerability in n/a, published on 29 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The IBM WebSphere DataPower XML Accelerator XA35, Low Latency Appliance XM70, Integration Appliance XI50, B2B Appliance XB60, and XML Security Gateway XS40 SOA Appliances before 3.8.0.0, when a QLOGIC Ethernet interface is used, allow remote attackers to cause a denial of service (interface outage) via malformed ICMP packets to the 0.0.0.0 destination IP address.

## Which versions are affected by CVE-2010-1612?

It affects 5 products.


Products: Ibm Websphere Datapower B2b Appliance Xb60, Ibm Websphere Datapower Datapower Integration Appliance Xi50, Ibm Websphere Datapower Low Latency Appliance Xm70, Ibm Websphere Datapower Xml Accelerator Xa35, Ibm Websphere Datapower Xml Security Gateway Xs40.

## How do I fix CVE-2010-1612?

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

## Is CVE-2010-1612 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1612 and fix it if it is affected.

What it is: CVE-2010-1612 is a medium-severity denial of service vulnerability in n/a, published on 29 Apr 2010. 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-2010-1612 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-2010-1612/ (Markdown: https://insights.sbomify.com/CVE-2010-1612/index.md)
```

## Sources

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

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