# CVE-2009-4919: Memory corruption in n/a

> Remote attackers can trigger a buffer overflow in Cisco ASA devices via long IKE attributes, potentially leading to code execution or denial of service.

- **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:** 29 Jun 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6hqc-c4rr-fj7q

## What is CVE-2009-4919?

CVE-2009-4919 is a critical memory corruption vulnerability in n/a, published on 29 Jun 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow on Cisco Adaptive Security Appliances (ASA) 5580 series devices with software before 8.1(2) allows remote attackers to have an unspecified impact via long IKE attributes, aka Bug ID CSCsu43121.

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

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

It affects 1 product.


Products: Cisco Asa 5580.

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

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

## Is CVE-2009-4919 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4912](https://insights.sbomify.com/CVE-2009-4912/): Auth bypass in n/a (critical 10.0)
- [CVE-2009-4911](https://insights.sbomify.com/CVE-2009-4911/): Denial of service in n/a (high 7.8)
- [CVE-2009-4914](https://insights.sbomify.com/CVE-2009-4914/): Denial of service in n/a (high 7.8)
- [CVE-2009-4915](https://insights.sbomify.com/CVE-2009-4915/): Denial of service in n/a (high 7.8)
- [CVE-2009-4917](https://insights.sbomify.com/CVE-2009-4917/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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