# CVE-2013-6718: Information disclosure in n/a

> Remote attackers can discover account names and passwords via an unspecified interface in IBM BladeCenter Advanced Management Module firmware.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5xv9-wc5r-crqg

## What is CVE-2013-6718?

CVE-2013-6718 is a medium-severity vulnerability in n/a, published on 1 Dec 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Advanced Management Module (AMM) with firmware 3.64B, 3.64C, and 3.64G for IBM BladeCenter systems allows remote attackers to discover account names and passwords via use of an unspecified interface.

Weakness: CWE-310

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

It affects 1 product.


Products: Ibm Advanced Management Module Firmware.

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

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

## Is CVE-2013-6718 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3935](https://insights.sbomify.com/CVE-2009-3935/): Other in n/a (critical 10.0)
- [CVE-2016-8232](https://insights.sbomify.com/CVE-2016-8232/): Cross-site scripting in Lenovo IBM BladeCenter HS22, HS22V, HS23, HS23E, HX5 Earlier than 66Z (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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