# CVE-2007-1491: Misconfiguration in n/a

> Avaya systems expose Tomcat AJP port 8009 externally, allowing unauthorized remote access and potential attacks from outside parties.

- **Severity:** Medium 5.2 (`AV:A/AC:L/Au:S/C:P/I:P/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:** 16 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4m85-jqvq-xx9c

## What is CVE-2007-1491?

CVE-2007-1491 is a medium-severity vulnerability in n/a, published on 16 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Tomcat in Avaya S87XX, S8500, and S8300 before CM 3.1.3, and Avaya SES allows connections from external interfaces via port 8009, which exposes it to attacks from outside parties.

## Which versions are affected by CVE-2007-1491?

It affects 4 products.


Products: Avaya S8300, Avaya S8500, Avaya S8700, Avaya Sip Enablement Services.

## How do I fix CVE-2007-1491?

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

## Is CVE-2007-1491 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1367](https://insights.sbomify.com/CVE-2007-1367/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1491 and fix it if it is affected.

What it is: CVE-2007-1491 is a medium-severity vulnerability in n/a, published on 16 Mar 2007. 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-2007-1491 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-2007-1491/ (Markdown: https://insights.sbomify.com/CVE-2007-1491/index.md)
```

## Sources

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

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