Belkin F9K1102 2.10.17 LockStatus/Login_Success access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability was found in Belkin F9K1102 2.10.17. It has been classified as critical. Affected is an unknown functionality. The manipulation of the argument LockStatus/Login_Success with an unknown input leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Belkin F9K1102 2 devices with firmware 2.10.17 rely on client-side JavaScript code for authorization, which allows remote attackers to obtain administrative privileges via certain changes to LockStatus and Login_Success values.

The weakness was disclosed 12/31/2015 (Website). The advisory is available at This vulnerability is traded as CVE-2015-5989 since 08/14/2015. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries 79960, 79961 and 79963 are pretty similar.




CPE 2.3infoedit

CPE 2.2infoedit


VulDB Meta Base Score: 8.5
VulDB Meta Temp Score: 8.5

VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Class: Privilege escalation
CWE: CWE-264
ATT&CK: T1068

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍


Threat Intelligenceinfoedit

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍


08/14/2015 🔍
12/31/2015 +139 days 🔍
12/31/2015 +0 days 🔍
01/02/2016 +2 days 🔍
05/25/2018 +874 days 🔍


Status: Not defined

CVE: CVE-2015-5989 (🔍)
See also: 🔍


Created: 01/02/2016 05:39 PM
Updated: 05/25/2018 10:15 AM
Changes: (1) source_cve_assigned
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!