# CVE-2007-5717: Command injection in n/a

> Remote attackers can execute arbitrary commands as root on Sun Fire server management processors via unspecified vectors in the embedded firmware.

- **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:** 30 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vf76-6hmj-g67c

## What is CVE-2007-5717?

CVE-2007-5717 is a critical command injection vulnerability in n/a, published on 30 Oct 2007. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in Sun Fire X2100 M2 and X2200 M2 Embedded Lights Out Manager (ELOM) on x86 before firmware 2.70 allows remote attackers to execute arbitrary commands as root on the Service Processor (SP) via unspecified vectors, a different vulnerability than CVE-2007-5170.

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

It affects 1 product.


Products: Sun Embedded Lights Out Manager.

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

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

## Is CVE-2007-5717 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5170](https://insights.sbomify.com/CVE-2007-5170/): Other in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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