OX App Suite up to 7.10.2 Access Control default permission

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

Summaryinfo

A vulnerability identified as critical has been detected in OX App Suite up to 7.10.2. Affected by this issue is some unknown functionality of the component Access Control. The manipulation leads to default permission. This vulnerability is referenced as CVE-2019-16716. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in OX App Suite up to 7.10.2 and classified as critical. This issue affects some unknown functionality of the component Access Control. The manipulation with an unknown input leads to a default permission vulnerability. Using CWE to declare the problem leads to CWE-276. During installation, installed file permissions are set to allow anyone to modify those files. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

OX App Suite through 7.10.2 has Incorrect Access Control.

The weakness was published 01/06/2020 as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The identification of this vulnerability is CVE-2019-16716 since 09/23/2019. The attack may be initiated remotely. A simple authentication is required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

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

Similar entry is available at VDB-148326. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.3

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

NVD Base Score: 6.6
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Default permission
CWE: CWE-276 / CWE-266
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

09/23/2019 🔍
01/06/2020 +105 days 🔍
01/07/2020 +1 days 🔍
03/19/2024 +1533 days 🔍

Sourcesinfo

Advisory: 155813
Status: Not defined

CVE: CVE-2019-16716 (🔍)
GCVE (CVE): GCVE-0-2019-16716
GCVE (VulDB): GCVE-100-148325
See also: 🔍

Entryinfo

Created: 01/07/2020 10:24
Updated: 03/19/2024 16:00
Changes: 01/07/2020 10:24 (38), 01/07/2020 10:29 (17), 03/19/2024 16:00 (17)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider 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!