# CVE-2009-2543: Security feature bypass in n/a

> Remote attackers can bypass malware detection in IBM Proventia security products by using modified ZIP or CAB archives.

- **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:** 20 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r6wx-j8f2-9xr4

## What is CVE-2009-2543?

CVE-2009-2543 is a critical vulnerability in n/a, published on 20 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple unspecified vulnerabilities in the IBM Proventia engine 4.9.0.0.44 20081231, as used in IBM Proventia Network Mail Security System, Network Mail Security System Virtual Appliance, Desktop Endpoint Security, Network Multi-Function Security (MFS), and possibly other products, allow remote attackers to bypass detection of malware via a modified (1) ZIP or (2) CAB archive, a related issue to CVE-2009-1240.

## Which versions are affected by CVE-2009-2543?

It affects 4 products.


Products: Ibm Proventia Desktop Endpoint Security, Ibm Proventia Network Mail Security System, Ibm Proventia Network Mail Security System Vitual Appliance, Ibm Proventia Network Multi-Function Security.

## How do I fix CVE-2009-2543?

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

## Is CVE-2009-2543 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2543 and fix it if it is affected.

What it is: CVE-2009-2543 is a critical vulnerability in n/a, published on 20 Jul 2009. 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-2009-2543 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-2009-2543/ (Markdown: https://insights.sbomify.com/CVE-2009-2543/index.md)
```

## Sources

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

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