LiveActive security incident?Get immediate response
CVE Record

CVE-2014-3519: The open_by_handle_at function in vzkernel before 042stab090.5 in the OpenVZ modification for the Linux ker...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a legacy OpenVZ container-isolation flaw. Under specific conditions, a user inside a container could bypass intended file-access boundaries and read arbitrary files on the underlying filesystem. The business risk is strongest for multi-tenant or hosted environments where container isolation is a security boundary. Exposure appears limited to legacy OpenVZ or Virtuozzo-style deployments using affected vzkernel builds, simfs, and containers granted CAP_DAC_READ_SEARCH. The provided affected-product metadata is incomplete, so inventory should focus on kernel build and storage configuration rather than product name alone. Prioritize this where legacy OpenVZ hosts support customer, partner, or untrusted workloads. The issue directly affects container isolation, but the evidence points to specific old configurations rather than broad modern Linux exposure. Mitigation focus: Update affected OpenVZ vzkernel systems to 042stab090.5 or later vendor guidance.; Apply relevant Virtuozzo or Parallels core updates referenced by the vendor advisories.; Remove CAP_DAC_READ_SEARCH from containers unless explicitly required..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-3519 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.