# CVE-2007-1093: Code injection in n/a

> Remote attackers can execute arbitrary code or cause denial of service in JP1/Cm2/Network Node Manager via unspecified vulnerabilities.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m79g-frxj-vppr

## What is CVE-2007-1093?

CVE-2007-1093 is a critical code injection vulnerability in n/a, published on 26 Feb 2007. It can be exploited over the network, with no action from the victim.

### Official description

Multiple unspecified vulnerabilities in JP1/Cm2/Network Node Manager (NNM) before 07-10-05, and before 08-00-02 in the 08-x series, allow remote attackers to execute arbitrary code, cause a denial of service, or trigger invalid Web utility behavior.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 6 products.


Products: Hitachi Cm2-Network Node Manager, Hitachi Cm2-Network Node Manager 250, Hitachi Jp1-Cm2-Network Node Manager, Hitachi Jp1-Cm2-Network Node Manager 250, Hitachi Jp1-Cm2-Network Node Manager Starter, Hitachi Jp1-Cm2-Network Node Manager Starter 250.

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

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

## Is CVE-2007-1093 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4793](https://insights.sbomify.com/CVE-2005-4793/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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