doorGets 7.0 routers/ajaxRouter.php uri Path pathname traversal

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 problematic has been detected in doorGets 7.0. This vulnerability affects unknown code of the file routers/ajaxRouter.php. This manipulation of the argument uri as part of Request causes pathname traversal (Path). The identification of this vulnerability is CVE-2019-11626. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in doorGets 7.0. It has been declared as problematic. Affected by this vulnerability is some unknown functionality of the file routers/ajaxRouter.php. The manipulation of the argument uri as part of a Request leads to a pathname traversal vulnerability (Path). The CWE definition for the vulnerability is CWE-21. As an impact it is known to affect confidentiality. The summary by CVE is:

routers/ajaxRouter.php in doorGets 7.0 has a web site physical path leakage vulnerability, as demonstrated by an ajax/index.php?uri=1234%5c request.

The bug was discovered 04/29/2019. The weakness was shared 04/30/2019. This vulnerability is known as CVE-2019-11626 since 04/30/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:routers/ajaxRouter.php it is possible to find vulnerable targets with Google Hacking.

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

The entries VDB-134268, VDB-134267, VDB-134266 and VDB-134265 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

License

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: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Name: Path
Class: Pathname traversal / Path
CWE: CWE-21 / CWE-22
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Google Hack: 🔍

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

04/29/2019 🔍
04/30/2019 +1 days 🔍
04/30/2019 +0 days 🔍
05/01/2019 +1 days 🔍
09/11/2023 +1594 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2019-11626 (🔍)
GCVE (CVE): GCVE-0-2019-11626
GCVE (VulDB): GCVE-100-134269
See also: 🔍

Entryinfo

Created: 05/01/2019 13:58
Updated: 09/11/2023 11:15
Changes: 05/01/2019 13:58 (57), 06/05/2020 10:24 (1), 09/11/2023 11:15 (3)
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!