# CVE-2007-0661: Missing authorization in n/a

> Remote attackers can issue arbitrary IPMI commands on Intel server BMCs when IPMI is enabled, potentially causing denial of service.

- **Severity:** Medium 5.4 (`AV:A/AC:M/Au:N/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:** 1 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5xjg-5mmc-43mv

## What is CVE-2007-0661?

CVE-2007-0661 is a medium-severity missing authorization vulnerability in n/a, published on 1 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Intel Enterprise Southbridge 2 Baseboard Management Controller (BMC), Intel Server Boards 5000XAL, S5000PAL, S5000PSL, S5000XVN, S5000VCL, S5000VSA, SC5400RA, and OEM Firmware for Intel Enterprise Southbridge Baseboard Management Controller before 20070119, when Intelligent Platform Management Interface (IPMI) is enabled, allow remote attackers to connect and issue arbitrary IPMI commands, possibly triggering a denial of service.

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

It affects 9 products.


Products: Intel Enterprise Southbridge 2 Bmc, Intel Enterprise Southbridge Bmc, Intel Server Board S5000pal, Intel Server Board S5000psl, Intel Server Board S5000vcl, Intel Server Board S5000vsa, Intel Server Board S5000xal, Intel Server Board S5000xvn, Intel Server Board Sc5400ra.

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

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

## Is CVE-2007-0661 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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