# CVE-2014-3519: Security feature bypass in n/a

> Local container users with specific capabilities can bypass container isolation to read arbitrary files on the host filesystem.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3xvv-h6m4-9qgx

## What is CVE-2014-3519?

CVE-2014-3519 is a medium-severity vulnerability in n/a, published on 1 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The open_by_handle_at function in vzkernel before 042stab090.5 in the OpenVZ modification for the Linux kernel 2.6.32, when using simfs, might allow local container users with CAP_DAC_READ_SEARCH capability to bypass an intended container protection mechanism and access arbitrary files on a filesystem via vectors related to use of the file_handle structure.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Openvz Vzkernel.

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

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

## Is CVE-2014-3519 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2239](https://insights.sbomify.com/CVE-2013-2239/): Information disclosure in n/a (medium 4.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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