# CVE-2015-7268: Security feature bypass in n/a

> Physically proximate attackers can bypass self-encrypting drive protection on specific laptops by triggering a soft reset and booting an alternative OS.

- **Severity:** Medium 4.2 (`CVSS:3.0/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4j4c-g46x-98wm

## What is CVE-2015-7268?

CVE-2015-7268 is a medium-severity vulnerability in n/a, published on 27 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Samsung 850 Pro and PM851 solid-state drives and Seagate ST500LT015 and ST500LT025 hard disk drives, when used on Windows and operating in Opal mode on Lenovo ThinkPad T440s laptops with BIOS 2.32 or ThinkPad W541 laptops with BIOS 2.21, or in Opal or eDrive mode on Dell Latitude E6410 laptops with BIOS A16 or Latitude E6430 laptops with BIOS A16, allow physically proximate attackers to bypass self-encrypting drive (SED) protection by triggering a soft reset and booting from an alternative OS, aka a "Forced Restart Attack."

Weakness: CWE-254

## Which versions are affected by CVE-2015-7268?

It affects 4 products.


Products: Samsung 850 Pro Firmware, Samsung Pm851 Firmware, Seagate St500lt015 Firmware, Seagate St500lt025 Firmware.

## How do I fix CVE-2015-7268?

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

## Is CVE-2015-7268 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7267](https://insights.sbomify.com/CVE-2015-7267/): Security feature bypass in n/a (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7268 and fix it if it is affected.

What it is: CVE-2015-7268 is a medium-severity vulnerability in n/a, published on 27 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7268 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-2015-7268/ (Markdown: https://insights.sbomify.com/CVE-2015-7268/index.md)
```

## Sources

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

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