Zendesk FON2601E-SE up to 1.1.7 DNS Amplification input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Zendesk FON2601E-SE, FON2601E-RE, FON2601E-FSW-S and FON2601E-FSW-B up to 1.1.7. This vulnerability affects unknown code of the component DNS Handler. Such manipulation leads to input validation (Amplification). This vulnerability is referenced as CVE-2019-6015. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in Zendesk FON2601E-SE, FON2601E-RE, FON2601E-FSW-S and FON2601E-FSW-B up to 1.1.7 and classified as problematic. Affected by this issue is some unknown functionality of the component DNS Handler. The manipulation with an unknown input leads to a input validation vulnerability (Amplification). Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is availability. CVE summarizes:
FON2601E-SE, FON2601E-RE, FON2601E-FSW-S, and FON2601E-FSW-B with firmware versions 1.1.7 and earlier contain an issue where they may behave as open resolvers. If this vulnerability is exploited, FON routers may be leveraged for DNS amplification attacks to some other entities.
The weakness was published 10/04/2019. This vulnerability is handled as CVE-2019-6015 since 01/10/2019. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: AmplificationClass: Input validation / Amplification
CWE: CWE-20
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/10/2019 🔍10/04/2019 🔍
10/05/2019 🔍
01/03/2024 🔍
Sources
Advisory: jvn.jpStatus: Not defined
CVE: CVE-2019-6015 (🔍)
GCVE (CVE): GCVE-0-2019-6015
GCVE (VulDB): GCVE-100-142970
Entry
Created: 10/05/2019 18:07Updated: 01/03/2024 15:40
Changes: 10/05/2019 18:07 (36), 09/23/2020 12:42 (17), 01/03/2024 15:40 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.