# CVE-2013-4031: Hardcoded credentials in n/a

> Remote attackers can exploit default IPMI credentials to control server power states and modify accounts on IBM servers.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7p2w-5xvj-v699

## What is CVE-2013-4031?

CVE-2013-4031 is a critical vulnerability in n/a, published on 9 Aug 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Intelligent Platform Management Interface (IPMI) implementation in Integrated Management Module (IMM) and Integrated Management Module II (IMM2) on IBM BladeCenter, Flex System, System x iDataPlex, and System x3### servers has a default password for the IPMI user account, which makes it easier for remote attackers to perform power-on, power-off, or reboot actions, or add or modify accounts, via unspecified vectors.

Weakness: CWE-255

## Which versions are affected by CVE-2013-4031?

It affects 30 products.


Products: Ibm Bladecenter, Ibm Flex System X220 Compute Node, Ibm Flex System X240 Compute Node, Ibm Flex System X440 Compute Node, Ibm System X3100 M4, Ibm System X3200 M3, Ibm System X3250 M3, Ibm System X3250 M4, Ibm System X3400 M2, Ibm System X3400 M3, Ibm System X3500 M2, Ibm System X3500 M3, Ibm System X3500 M4, Ibm System X3530 M4, Ibm System X3550 M2, Ibm System X3550 M3, Ibm System X3550 M4, Ibm System X3620 M3, Ibm System X3630 M3, Ibm System X3630 M4 and 10 more.

## How do I fix CVE-2013-4031?

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

## Is CVE-2013-4031 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4030](https://insights.sbomify.com/CVE-2013-4030/): Weak cryptography in n/a (medium 4.3)
- [CVE-2013-4037](https://insights.sbomify.com/CVE-2013-4037/): Information disclosure in n/a (medium 4.3)
- [CVE-2013-4038](https://insights.sbomify.com/CVE-2013-4038/): Information disclosure in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4031 and fix it if it is affected.

What it is: CVE-2013-4031 is a critical vulnerability in n/a, published on 9 Aug 2013. 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-2013-4031 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-2013-4031/ (Markdown: https://insights.sbomify.com/CVE-2013-4031/index.md)
```

## Sources

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

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