What is the CVSS score of CVE-2017-8116?

CVE-2017-8116 has a CVSS 3.0 base score of 9.8 (Critical). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 7.5%.

Is there a public PoC exploit available for CVE-2017-8116?

Yes, a public proof-of-concept exploit is available for CVE-2017-8116. Prioritise patching immediately. EPSS: 7.5%.

Rut900 Firmware CVE-2017-8116

CRITICAL

OS Command Injection (CWE-78)

2017-07-03 cve@mitre.org

Command Injection Rut900 Firmware Rut905 Firmware Rut950 Firmware Rut955 Firmware

9.8

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jul 03, 2017 - 16:29 cve.org

CRITICAL 9.8

DescriptionCVE.org

AnalysisAI

The management interface for the Teltonika RUT9XX routers (aka LuCI) with firmware 00.03.265 and earlier allows remote attackers to execute arbitrary commands with root privileges via shell. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. The management interface for the Teltonika RUT9XX routers (aka LuCI) with firmware 00.03.265 and earlier allows remote attackers to execute arbitrary commands with root privileges via shell metacharacters in the username parameter in a login request. Affected products include: Teltonika Rut900 Firmware, Teltonika Rut905 Firmware, Teltonika Rut950 Firmware, Teltonika Rut955 Firmware.

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.