# CVE-2011-5117: Race condition in n/a

> Physically proximate attackers can bypass full-disk encryption by exploiting a race condition in credential removal timing.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 24 Aug 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r9fg-3g6m-68g9

## What is CVE-2011-5117?

CVE-2011-5117 is a medium-severity vulnerability in n/a, published on 24 Aug 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sophos SafeGuard Enterprise Device Encryption 5.x through 5.50.8.13, Sophos SafeGuard Easy Device Encryption Client 5.50.x, and Sophos Disk Encryption 5.50.x have a delay before removal of (1) out-of-date credentials and (2) invalid credentials, which allows physically proximate attackers to defeat the full-disk encryption feature by leveraging knowledge of these credentials.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2011-5117?

It affects 3 products.


Products: Sophos Disk Encryption, Sophos Safeguard Easy Device Encryption Client, Sophos Safeguard Enterprise Device Encryption.

## How do I fix CVE-2011-5117?

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

## Is CVE-2011-5117 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-5117 and fix it if it is affected.

What it is: CVE-2011-5117 is a medium-severity vulnerability in n/a, published on 24 Aug 2012. 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-2011-5117 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-2011-5117/ (Markdown: https://insights.sbomify.com/CVE-2011-5117/index.md)
```

## Sources

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

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