Menu

Star on GitHub · 3.2k

CVE-2015-3400

4.3 · MEDIUM

sharenfs 0.6.4, when built with commits bcdd594 and 7d08880 from the zfs repository, provides world readable access to the shared zfs file system, which might allow remote authenticated users to ob…

Published Oct 18, 2017CWE-200EPSS 1.65%

Overview

CVE-2015-3400 is a medium-severity vulnerability. It was published on October 18, 2017 and has a CVSS 3.0 base score of 4.3 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

sharenfs 0.6.4, when built with commits bcdd594 and 7d08880 from the zfs repository, provides world readable access to the shared zfs file system, which might allow remote authenticated users to obtain sensitive information by reading shared files.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2015-3400?

CVE-2015-3400 is a medium-severity vulnerability. It was published on October 18, 2017 and has a CVSS 3.0 base score of 4.3 (MEDIUM).

How severe is CVE-2015-3400?

This vulnerability has a CVSS 3.0 base score of 4.3, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2015-3400?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2015-3400?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2015-3400 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2015

View all