What is the CVSS score of CVE-2015-2950?

CVE-2015-2950 has a CVSS 2.0 base score of 6.4 (Medium). CVSS vector: AV:N/AC:L/Au:N/C:N/I:P/A:P. EPSS exploitation probability: 0.6%.

Is there a patch available for CVE-2015-2950?

Yes, a patch is available for CVE-2015-2950. Update the affected software to the latest version immediately.

Open Explorer Beta CVE-2015-2950

MEDIUM

Path Traversal (CWE-22)

2015-06-05 vultures@jpcert.or.jp

Path Traversal Google Open Explorer Beta

6.4

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

6.4 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

None

Integrity

Availability

Lifecycle Timeline

CVE Published

Jun 05, 2015 - 10:59 cve.org

MEDIUM 6.4

DescriptionCVE.org

Directory traversal vulnerability in the Brandon Bowles Open Explorer application before 0.254 Beta for Android allows remote attackers to write to arbitrary files via a crafted filename.

AnalysisAI

Directory traversal vulnerability in the Brandon Bowles Open Explorer application before 0.254 Beta for Android allows remote attackers to write to arbitrary files via a crafted filename. Rated medium severity (CVSS 6.4), this vulnerability is remotely exploitable, low attack complexity. This Path Traversal vulnerability could allow attackers to access files and directories outside the intended path.

Technical ContextAI

This vulnerability is classified as Path Traversal (CWE-22), which allows attackers to access files and directories outside the intended path. Directory traversal vulnerability in the Brandon Bowles Open Explorer application before 0.254 Beta for Android allows remote attackers to write to arbitrary files via a crafted filename. Affected products include: Open Explorer Beta Project Open Explorer Beta. Version information: before 0.254.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate and canonicalize file paths. Use chroot or sandboxing. Reject input containing path separators or '../' sequences.