What is the CVSS score of CVE-2013-5758?

CVE-2013-5758 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: 11.7%.

Is there a public PoC exploit available for CVE-2013-5758?

Yes, a public proof-of-concept exploit is available for CVE-2013-5758. Prioritise patching immediately. EPSS: 11.7%.

Sip T38G CVE-2013-5758

CRITICAL

OS Command Injection (CWE-78)

2014-08-03 cve@mitre.org

Command Injection Sip T38G

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

Aug 03, 2014 - 18:55 cve.org

CRITICAL 9.0

DescriptionCVE.org

cgi-bin/cgiServer.exx in Yealink VoIP Phone SIP-T38G allows remote authenticated users to execute arbitrary commands by calling the system method in the body of a request, as demonstrated by running unauthorized services, changing directory permissions, and modifying files.

AnalysisAI

cgi-bin/cgiServer.exx in Yealink VoIP Phone SIP-T38G allows remote authenticated users to execute arbitrary commands by calling the system method in the body of a request, as demonstrated by running. Rated critical severity (CVSS 9.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 11.7%.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. cgi-bin/cgiServer.exx in Yealink VoIP Phone SIP-T38G allows remote authenticated users to execute arbitrary commands by calling the system method in the body of a request, as demonstrated by running unauthorized services, changing directory permissions, and modifying files. Affected products include: Yealink Sip-T38G.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Avoid passing user input to shell commands. Use language-specific APIs instead of shell execution. Apply strict input validation with allowlists.