# CVE-2009-0618: Privilege escalation in n/a

> Remote attackers can gain privileges, cause denial of service, or read sensitive configuration files in Cisco ANM Java agent.

- **Severity:** High 8.5 (`AV:N/AC:L/Au:N/C:P/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2009
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2crq-wx4p-2m52

## What is CVE-2009-0618?

CVE-2009-0618 is a high-severity vulnerability in n/a, published on 26 Feb 2009. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Java agent in Cisco Application Networking Manager (ANM) before 2.0 Update A allows remote attackers to gain privileges, and cause a denial of service (service outage) by stopping processes, or obtain sensitive information by reading configuration files.

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

It affects 1 product.


Products: Cisco Application Networking Manager.

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

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

## Is CVE-2009-0618 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0616](https://insights.sbomify.com/CVE-2009-0616/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2009-0617](https://insights.sbomify.com/CVE-2009-0617/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2015-0651](https://insights.sbomify.com/CVE-2015-0651/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-1196](https://insights.sbomify.com/CVE-2013-1196/): Privilege escalation in n/a (medium 6.8)
- [CVE-2013-1125](https://insights.sbomify.com/CVE-2013-1125/): Privilege escalation in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0618 is a high-severity vulnerability in n/a, published on 26 Feb 2009. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-0618 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-0618/ (Markdown: https://insights.sbomify.com/CVE-2009-0618/index.md)
```

## Sources

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

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