# CVE-2014-4768: Denial of service in n/a

> Privileged remote attackers can cause a temporary denial of service on IBM x86 servers by enabling legacy boot mode via UEFI.

- **Severity:** Low 2.1 (`AV:N/AC:H/Au:S/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-55mm-gwv2-2mm5

## What is CVE-2014-4768?

CVE-2014-4768 is a low-severity denial of service vulnerability in n/a, published on 28 Jun 2015. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM Unified Extensible Firmware Interface (UEFI) on Flex System x880 X6, System x3850 X6, and System x3950 X6 devices allows remote authenticated users to cause an unspecified temporary denial of service by using privileged access to enable a legacy boot mode.

## Which versions are affected by CVE-2014-4768?

It affects 1 product.


Products: Ibm Uefi.

## How do I fix CVE-2014-4768?

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

## Is CVE-2014-4768 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4768 and fix it if it is affected.

What it is: CVE-2014-4768 is a low-severity denial of service vulnerability in n/a, published on 28 Jun 2015. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-4768 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-2014-4768/ (Markdown: https://insights.sbomify.com/CVE-2014-4768/index.md)
```

## Sources

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

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