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

CVE-2015-0925 has a CVSS 2.0 base score of 9.0 (Critical). CVSS vector: AV:N/AC:L/Au:S/C:C/I:C/A:C. EPSS exploitation probability: 68.3%.

Is there a public PoC exploit available for CVE-2015-0925?

Yes, a public proof-of-concept exploit is available for CVE-2015-0925. Prioritise patching immediately. EPSS: 68.3%.

Ipass Open Mobile CVE-2015-0925

CRITICAL

Code Injection (CWE-94)

2015-01-22 cret@cert.org

RCE Code Injection Microsoft Ipass Open Mobile

9.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

9.0 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Jan 22, 2015 - 14:02 cve.org

CRITICAL 9.0

DescriptionCVE.org

The client in iPass Open Mobile before 2.4.5 on Windows allows remote authenticated users to execute arbitrary code via a DLL pathname in a crafted Unicode string that is improperly handled by a subprocess reached through a named pipe, as demonstrated by a UNC share pathname.

AnalysisAI

The client in iPass Open Mobile before 2.4.5 on Windows allows remote authenticated users to execute arbitrary code via a DLL pathname in a crafted Unicode string that is improperly handled by a. Rated critical severity (CVSS 9.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 68.3%.

Technical ContextAI

This vulnerability is classified as Code Injection (CWE-94), which allows attackers to inject and execute arbitrary code within the application. The client in iPass Open Mobile before 2.4.5 on Windows allows remote authenticated users to execute arbitrary code via a DLL pathname in a crafted Unicode string that is improperly handled by a subprocess reached through a named pipe, as demonstrated by a UNC share pathname. Affected products include: Ipass Ipass Open Mobile. Version information: before 2.4.5.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Never evaluate user-controlled input as code. Use sandboxing, disable dangerous functions, apply strict input validation.