CVE-2015-5252

Public on

Last Modified: UTC

Insights vulnerability analysis

View exposed systems

Description

An access flaw was found in the way Samba verified symbolic links when creating new files on a Samba share. A remote attacker could exploit this flaw to gain access to files outside of Samba's share path.

An access flaw was found in the way Samba verified symbolic links when creating new files on a Samba share. A remote attacker could exploit this flaw to gain access to files outside of Samba's share path.

Additional information

  • Bugzilla 1290288: samba: Insufficient symlink verification in smbd
  • CWE-41: Improper Resolution of Path Equivalence
  • FAQ: Frequently asked questions about CVE-2015-5252

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v2 Score Breakdown
Red HatNVD

CVSS v2 Base Score

4.3

5

Attack Vector

Network

Network

Access Complexity

Medium

Low

Authentication

None

None

Confidentiality Impact

None

None

Integrity Impact

Partial

Partial

Availability Impact

None

None

CVSS v2 Vector

Red Hat: AV:N/AC:M/Au:N/C:N/I:P/A:N

NVD: AV:N/AC:L/Au:N/C:N/I:P/A:N

Acknowledgements

Red Hat would like to thank Samba project for reporting this issue.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

What can I do if my product is listed as "Will not fix"?

What can I do if my product is listed as "Fix deferred"?

What is a mitigation?

I have a Red Hat product but it is not in the above list, is it affected?

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

Want to get errata notifications? Sign up here.