| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Corega CG-WLBARAGM. Impacted is an unknown function of the component Proxy Service. The manipulation leads to Remote Code Execution (Routing). This vulnerability is uniquely identified as CVE-2015-7793. No exploit exists. It is recommended to apply restrictive firewalling.
Details
A vulnerability was found in Corega CG-WLBARAGM (affected version unknown) and classified as critical. This issue affects an unknown functionality of the component Proxy Service. The manipulation with an unknown input leads to a code vulnerability (Routing). Using CWE to declare the problem leads to CWE-17. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Corega CG-WLBARAGM devices provide an open proxy service, which allows remote attackers to trigger outbound network traffic via unspecified vectors.
The weakness was disclosed 12/30/2015 (Website). The advisory is shared at jvndb.jvn.jp. The identification of this vulnerability is CVE-2015-7793 since 10/09/2015. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
Addressing this vulnerability is possible by firewalling .
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: RoutingClass: Code / Routing
CWE: CWE-17
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: FirewallStatus: 🔍
0-Day Time: 🔍
Timeline
10/09/2015 🔍12/30/2015 🔍
12/30/2015 🔍
01/02/2016 🔍
05/26/2018 🔍
Sources
Advisory: jvndb.jvn.jpStatus: Not defined
Confirmation: 🔍
CVE: CVE-2015-7793 (🔍)
GCVE (CVE): GCVE-0-2015-7793
GCVE (VulDB): GCVE-100-79997
Entry
Created: 01/02/2016 17:45Updated: 05/26/2018 07:44
Changes: 01/02/2016 17:45 (55), 05/26/2018 07:44 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.