# CVE-2013-4805: Auth bypass in n/a

> Remote attackers can bypass authentication in HP Integrated Lights-Out firmware, gaining unauthorized access to server management interfaces.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 3 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c5hf-72cj-jcx7

## What is CVE-2013-4805?

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

### Official description

Unspecified vulnerability in HP Integrated Lights-Out 3 (aka iLO3) firmware before 1.60 and 4 (aka iLO4) firmware before 1.30 allows remote attackers to bypass authentication via unknown vectors.

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

It affects 1 product.


Products: Hp Integrated Lights-Out Firmware.

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

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

## Is CVE-2013-4805 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-5436](https://insights.sbomify.com/CVE-2015-5436/): A potential security vulnerability has been identified with HP Integrated Lights-Out 4 (iLO 4) firmware version 2.11 and later, but prior to version 2.30. (high 7.5)
- [CVE-2023-28092](https://insights.sbomify.com/CVE-2023-28092/): A potential security vulnerability has been identified in HPE ProLiant RL300 Gen11 Server. (medium 6.1)
- [CVE-2004-0525](https://insights.sbomify.com/CVE-2004-0525/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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