# CVE-2008-3081: Command injection in n/a

> Remote authenticated administrators can execute arbitrary commands on Avaya Message Storage Server via input validation flaws in the web management interface.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q4cf-5q7c-rjwq

## What is CVE-2008-3081?

CVE-2008-3081 is a medium-severity command injection vulnerability in n/a, published on 9 Jul 2008. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple unspecified "input validation" vulnerabilities in the Web management interface (aka Messaging Administration interface) in Avaya Message Storage Server (MSS) 3.x and 4.0, and possibly Communication Manager 3.1.x, allow remote authenticated administrators to execute arbitrary commands as user vexvm via vectors related to (1) SFTP Remote Store configuration; (2) remote FTP storage settings; (3) name server lookup; (4) pinging another host; (5) TCP/IP Networking parameter configuration; (6) the external hosts configuration main page; (7) adding and changing external hosts; (8) Windows domain parameter configuration; (9) date, time, and NTP server configuration; (10) alarm settings; (11) the command line history form; (12) the maintenance form; and (13) the server events form.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-3081?

It affects 1 product.


Products: Avaya Messaging Storage Server.

## How do I fix CVE-2008-3081?

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

## Is CVE-2008-3081 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3081 and fix it if it is affected.

What it is: CVE-2008-3081 is a medium-severity command injection vulnerability in n/a, published on 9 Jul 2008. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-3081 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-2008-3081/ (Markdown: https://insights.sbomify.com/CVE-2008-3081/index.md)
```

## Sources

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

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