Dynacolor FCM-MB40 1.2.0.0 /usr/sbin/default.sh Persistent 7pk security

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.
6.9$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in Dynacolor FCM-MB40 1.2.0.0. Affected is an unknown function of the file /usr/sbin/default.sh. The manipulation results in 7pk security (Persistent). This vulnerability is identified as CVE-2019-13402. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical has been found in Dynacolor FCM-MB40 1.2.0.0. Affected is an unknown function of the file /usr/sbin/default.sh. The manipulation with an unknown input leads to a 7pk security vulnerability (Persistent). CWE is classifying the issue as CWE-254. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

/usr/sbin/default.sh and /usr/apache/htdocs/cgi-bin/admin/hardfactorydefault.cgi on Dynacolor FCM-MB40 v1.2.0.0 devices implement an incomplete factory-reset process. A backdoor can persist because neither system accounts nor the set of services is reset.

The weakness was released 07/08/2019. This vulnerability is traded as CVE-2019-13402 since 07/07/2019. The exploitability is told to be difficult. It is possible to launch the attack remotely. The successful exploitation requires a authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1211 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.

Entries connected to this vulnerability are available at VDB-137465, VDB-137464, VDB-137463 and VDB-137462. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.9
VulDB Meta Temp Score: 6.9

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

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

NVD Base Score: 🔍

Exploitinginfo

Name: Persistent
Class: 7pk security / Persistent
CWE: CWE-254
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

07/07/2019 🔍
07/08/2019 +1 days 🔍
07/08/2019 +0 days 🔍
10/18/2023 +1563 days 🔍

Sourcesinfo

Advisory: xor.cat
Status: Not defined

CVE: CVE-2019-13402 (🔍)
GCVE (CVE): GCVE-0-2019-13402
GCVE (VulDB): GCVE-100-137466
See also: 🔍

Entryinfo

Created: 07/08/2019 08:17
Updated: 10/18/2023 10:40
Changes: 07/08/2019 08:17 (38), 07/02/2020 10:47 (17), 10/18/2023 10:40 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!