What is the CVSS score of CVE-2019-15051?

CVE-2019-15051 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 3.3%.

Is there a public PoC exploit available for CVE-2019-15051?

Yes, a public proof-of-concept exploit is available for CVE-2019-15051. Prioritise patching immediately. EPSS: 3.3%.

Uagate Si Firmware CVE-2019-15051

HIGH

Command Injection (CWE-77)

2019-10-10 cve@mitre.org

Command Injection Uagate Si Firmware Uagate Mb Firmware Uagate 840D Firmware

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Oct 10, 2019 - 20:15 nvd

HIGH 8.8

DescriptionNVD

An issue was discovered in Softing uaGate (SI, MB, 840D) firmware through 1.71.00.1225. A CGI script is vulnerable to command injection via a maliciously crafted form parameter.

AnalysisAI

An issue was discovered in Softing uaGate (SI, MB, 840D) firmware through 1.71.00.1225. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Command Injection (CWE-77), which allows attackers to inject arbitrary commands into system command execution. An issue was discovered in Softing uaGate (SI, MB, 840D) firmware through 1.71.00.1225. A CGI script is vulnerable to command injection via a maliciously crafted form parameter. Affected products include: Softing Uagate Si Firmware, Softing Uagate Mb Firmware, Softing Uagate 840D Firmware. Version information: through 1.71.00.1225..

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use parameterized APIs, avoid shell execution, validate input with strict allowlists.